# SE-0263: Add a String Initializer with Access to Uninitialized Storage **URL:** \ **Category:** Proposal Reviews\ **Created:** [July 30, 2019, 6:14am UTC](https://forums.swift.org/t/se-0263-add-a-string-initializer-with-access-to-uninitialized-storage/27417 "2019-07-30T06:14:02Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![jawbroken](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jawbroken](https://forums.swift.org/u/jawbroken)\ **Post date:** [July 30, 2019, 12:41pm UTC](https://forums.swift.org/t/se-0263-add-a-string-initializer-with-access-to-uninitialized-storage/27417/9 "2019-07-30T12:41:53Z")
Perhaps, but on the other hand there is [`withUnsafeBytes(_:)` on Array](https://developer.apple.com/documentation/swift/array/2635991-withunsafebytes) and [`withUnsafeBytes(of:_:)`](https://developer.apple.com/documentation/swift/2998148-withunsafebytes) and the aforementioned [`init(unsafeUninitializedCapacity:initializingWith:)` on Array](https://developer.apple.com/documentation/swift/array/3200717-init), so the precedent/logic isn't that clear here. Edit: I'm not sure `withContiguousStorageIfAvailable` was that great a name, really. When looking into the history here, this API was [proposed and reviewed](https://forums.swift.org/t/review-2-of-se-0237-introduce-withunsafe-mutable-bufferpointerifsupported-methods/18418/5) with the name `withUnsafeBufferPointerIfAvailable`. The name change seems to have been [made at the last minute after the end of the review](https://github.com/apple/swift-evolution/commit/5c28a57f3d1ea01dd4c8518cd503962f33269724#diff-48f6bc7b9a47a356abfe5fdf4403dd59) for reasons I couldn't find and don't appear to have been mentioned in the [acceptance rationale](https://forums.swift.org/t/accepted-with-modifications-se-0237-introduce-with-contiguous-mutable-storage-if-available-methods/18713). Strange. --- _[View the full topic](https://forums.swift.org/t/se-0263-add-a-string-initializer-with-access-to-uninitialized-storage/27417)._