# \[Pitch\] Safe Access to Contiguous Storage

**URL:** <https://forums.swift.org/t/pitch-safe-access-to-contiguous-storage/69888>\
**Category:** Pitches\
**Created:** [February 6, 2024, 11:03pm UTC](https://forums.swift.org/t/pitch-safe-access-to-contiguous-storage/69888 "2024-02-06T23:03:46Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![Karl](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@Karl](https://forums.swift.org/u/Karl)\
**Post date:** [February 14, 2024, 6:47pm UTC](https://forums.swift.org/t/pitch-safe-access-to-contiguous-storage/69888/28 "2024-02-14T18:47:09Z")

</div>

Related to this point, it's worth considering whether we might want "borrowed" versions of other standard library types.

For instance, a [recent pitch](https://forums.swift.org/t/pitch-unicode-processing-apis/69294) suggested that we might add a type called `Unicode.UTF8.ValidBufferView` for text processing over non-owned storage. What if we instead called that a `BorrowedString`?

There would be nice some symmetry to having both `BorrowedArray` and `BorrowedString`, and I think having that as a more established pattern could minimise some of your concerns.

Anyway, I don't want to labour the point too much because my actual opinion is that `BorrowedBuffer` is also fine. But it's worth thinking about these things.

---

_[View the full topic](https://forums.swift.org/t/pitch-safe-access-to-contiguous-storage/69888)._