[swift-evolution] [Review] SE-0138 UnsafeBytes
davesweeris at mac.com
Wed Sep 7 09:56:47 CDT 2016
> On Sep 7, 2016, at 05:48, Karl Wagner via swift-evolution <swift-evolution at swift.org> wrote:
> >> 1. It points into memory that it does not own. The developer must do something to to manage the memory’s lifetime.
> Isn't that just a pointer? Is it really necessary to say "unsafe" and "pointer"?
> And if we did want to make it explicit, perhaps we say "unowned" instead, to make it clear how it is unsafe. "RawBufferPointer"/"UnownedRawBufferPointer" sound pretty good to me. You can derive some pretty solid expectations from those names.
Yeah, I didn't realize exactly what "unsafe" meant until quite recently.
- Dave Sweeris
More information about the swift-evolution