<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 Dec 16, 2015, at 2:40 PM, Joe Groff 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=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 16, 2015, at 2:25 PM, Jacob Bandes-Storch 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=""><div dir="ltr" class="">Is there a reason that this couldn't be made to work?<div class=""><p class=""><span class=""> let</span><span class=""> ptr: </span><span class="">UnsafePointer</span><span class=""><</span><span class="">Void</span><span class="">> = &x</span></p></div></div></div></blockquote></div>Yeah, that could be made to work, and give an error if `x` isn't known to be a stored property.</div></div></blockquote><br class=""></div><div>However, in the face of resilience, that could only be known if x were explicitly declared to be fragile, or within the current module.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>