> We’re thinking about it but there are no plans for Swift 3 in this respect
I didn't mean to imply otherwise. What I was trying to say is that it's on your
team's radar and trying to propose it probably won't be especially helpful.
--
Brent Royal-Gordon
Sent from my iPhone
Hi Remy, Brent,
We’re thinking about it but there are no plans for Swift 3 in this respect
(although I think we’re going to keep the NS prefix on these types).
One of the complexities with this type is its performance characteristics,
especially when used with CoreData (the reason it was
> Unlike its companion collections like NSArray, NSDictionary, and NSSet,
> NSOrdered is still a class rather than a struct and has a subclass that is
> still NSMutableOrderedSet. This should probably receive the same treatment as
> the other classes
Swift Evolution proposal SE-0069
