<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><div><span></span></div><div><div></div><div>See below.</div><div><br>On Dec 6, 2017, at 02:45, Nick Keets via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>Apologies, I may have misunderstood you. What I wanted to say is that I see no problem allowing "dangerous" stuff that may be abused. </div></blockquote><br><div>You see no problem with danger and abuse?</div><div><br></div><div>I guess we have differing philosophies...</div><div><br></div><div><a href="https://developer.apple.com/swift/">https://developer.apple.com/swift/</a> states:</div><div><br></div><div>“<span style="background-color: rgba(255, 255, 255, 0);">Swift eliminates entire classes of unsafe code.”</span></div><div><br></div><div>Lets keep it that way.</div><div><br></div><div>I’m all for this proposal if it can be tweaked to where any of the dangerous invocations contain the word, “Unsafe”, or equivalent.</div><div><br></div><div>~Jon</div><div><br></div><div><br></div>
</div></div></body></html>