[swift-evolution] [Review] SE-0055 Make unsafe pointer nullability explicit using Optional

Jordan Rose jordan_rose at apple.com
Mon Mar 28 12:45:02 CDT 2016

> On Mar 26, 2016, at 9:15, Антон Жилин via swift-evolution <swift-evolution at swift.org> wrote:
> But we currently have a terser form, and it's arguably clear from it that Pointer can be null.

For the record, I literally talked to someone last week who didn't know that UnsafePointer can be null. :-) They thought we'd already implemented this and there was a bug in the importer.

> Overall, separating strongly connected concepts and then tying them together using compiler magic just can't have a reasonable explanation. ~0x0 in UnsafeBufferPointer is utterly rediculous.

I'm not sure what this comment refers to. Can you explain?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160328/f9280033/attachment.html>

More information about the swift-evolution mailing list