> On Dec 16, 2015, at 2:40 PM, Joe Groff via swift-evolution > <[email protected]> wrote: > > >> On Dec 16, 2015, at 2:25 PM, Jacob Bandes-Storch via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> Is there a reason that this couldn't be made to work? >> let ptr: UnsafePointer<Void> = &x >> > Yeah, that could be made to work, and give an error if `x` isn't known to be > a stored property.
However, in the face of resilience, that could only be known if x were explicitly declared to be fragile, or within the current module. -Chris
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
