<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="">As was pointed out to me in the bug report, the preferred way to get a pointer is to use<div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 9px; line-height: normal; font-family: Menlo; color: rgb(61, 29, 129);" class=""><span style="font-variant-ligatures: no-common-ligatures; color: #703daa" class="">Unmanaged</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class="">.</span><span style="font-variant-ligatures: no-common-ligatures" class="">passUnretained</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class="">(</span><span style="font-variant-ligatures: no-common-ligatures; color: #4f8187" class="">obj</span><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class="">).toOpaque()</span></div></div><div style="margin: 0px; font-size: 9px; line-height: normal; font-family: Menlo; color: rgb(61, 29, 129);" class=""><span style="font-variant-ligatures: no-common-ligatures; color: #000000" class=""><br class=""></span></div><div style="margin: 0px; line-height: normal;" class="">I see a few issues, though (aside from toOpaque() missing in Xcode 8b1, haven't installed b2 yet):</div><div style="margin: 0px; line-height: normal;" class=""><br class=""></div><div style="margin: 0px; line-height: normal;" class="">- it is quite a verbose way of something I consider should be trivial - getting an address of an object.</div><div style="margin: 0px; line-height: normal;" class="">- it requires the caller to deal with retain cycle which I don't think should be explicit for getting an address of an object.</div><div style="margin: 0px; line-height: normal;" class=""><br class=""></div><div style="margin: 0px; line-height: normal;" class="">I'd personally leave it in the language as it feels similar to dynamicType(obj) and can be a nice-to-have debugging tool.</div><div style="margin: 0px; line-height: normal;" class=""><br class=""></div><div style="margin: 0px; line-height: normal;" class="">The most confusing part about unsafeAddress(of:) is implicit bridging which creates a new instance e.g. in case of String, in order to satisfy the AnyObject requirement. Fortunately, this will get eliminated by SE-0072 and Unmanaged suffered from the same issue, though it required you to specify either Unmanaged<NSString> or Unmanaged<AnyObject>.</div><div style="margin: 0px; line-height: normal;" class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Jul 6, 2016, at 8:03 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=""><br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">* <b class="">Remove unsafeAddressOf</b>. "We are not aware of any real use cases for it. If there are any, it should be renamed to unsafeAddress(of:) to follow the guidelines." (<a href="https://bugs.swift.org/browse/SR-1957" target="_blank" class="">https://bugs.swift.org/browse/SR-1957</a> <a class="">rdar://problem/18589289</a>)<br class=""></div><div class=""><br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">Oops, I just responded to this on another thread. Pasting:</div><div class=""><br class=""></div><div style="font-size:12.8px" class="">It's minor, but I use unsafeAddressOf regularly for writing `description` methods:</div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class=""> var description: String {</div><div style="font-size:12.8px" class=""> return "<\(self.dynamicType): \(unsafeAddressOf(self))>{ more info here... }"</div><div style="font-size:12.8px" class=""> }</div><div style="font-size:12.8px" class=""><br class=""></div><div class=""><span style="font-size:12.8px" class="">I guess this would be covered by some generalized solution for format specifiers in string interpolations, but I gather that won't happen for quite a while...</span> </div></div></div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>