Got it. In that case, count me in as +1 for most of the proposal but -1 on AttributedString and its ilk. I agree with you and others that types which are slated to receive the URL/NSURL treatment shouldn't go through an interim renaming dance.
On Mon, May 9, 2016 at 20:53 Brent Royal-Gordon <[email protected]> wrote: > > Unless I'm mistaken, NSURL is not among the types being renamed in this > proposal? > > It is not, because it's already receiving a value-type equivalent. But > types like `NSAttributedString`, which the Foundation team eventually > intends to provide value-type equivalents for, *are* in the proposal. I'm > merely illustrating the problem by using a type which we've already decided > will get a value-type equivalent. > > -- > Brent Royal-Gordon > Architechies > >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
