> On Sep 7, 2016, at 05:48, Karl Wagner via swift-evolution > <[email protected]> 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 _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
