on Wed Jul 06 2016, Jacob Bandes-Storch <[email protected]> wrote:
>> * *Remove unsafeAddressOf*. "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." (https://bugs.swift.org/browse/SR-1957 >> rdar://problem/18589289) >> >> > Oops, I just responded to this on another thread. Pasting: > > It's minor, but I use unsafeAddressOf regularly for writing `description` > methods: > > var description: String { > return "<\(self.dynamicType): \(unsafeAddressOf(self))>{ more info > here... }" > } > > 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... If we remove unsafeAddressOf, we have no way to get the address of an immutable variable. A mutable variable can be passed inout to a function taking an UnsafePointer, but you can't add & to an immutable binding. That's a loss I'm willing to take. I just wanted to point out exactly what we will have no way to accomplish if we remove unsafeAddressOf. -- Dave _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
