<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 26, 2016, at 9:15, Антон Жилин via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">But we currently have a terser form, and it's arguably clear from it that Pointer can be null.</span></div></blockquote></div><br class=""><div class="">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.</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class="">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.</blockquote></div></div><div class=""><br class=""></div><div class="">I'm not sure what this comment refers to. Can you explain?</div><div class=""><br class=""></div><div class="">Jordan</div></body></html>