<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="">I know I know. <div class=""><br class=""></div><div class="">I should have framed this as removing NilLiteralConvertible from Optional and supplying it with a new keyword.</div><div class=""><br class=""></div><div class="">I don’t find nil to adequately represent what it is doing with optionals. It *looks* like it is setting a object to nil when this really isn’t the case. The optional is still very valid with a value of .none.</div><div class=""><br class=""></div><div class="">nil in swift is pretty different from nil in other languages. nil is mostly unsafe to access in other languages where in swift it is just a value representing no contained value.</div><div class=""><br class=""></div><div class="">nil in swift: safe to access. In other languages? Not so much (at least C / C++)</div><div class=""><br class=""></div><div class="">Brandon</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 8, 2016, at 11:51 AM, David Waite <<a href="mailto:david@alkaline-solutions.com" class="">david@alkaline-solutions.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; 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="">i</span></div></blockquote></div><br class=""></div></body></html>