> Proposal link: > > https://github.com/apple/swift-evolution/blob/master/proposals/0086-drop-foundation-ns.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0086-drop-foundation-ns.md> > Reply text > >> What is your evaluation of the proposal? > +1 to all except renaming classes that are planned in the future to become > value types, and the NSCoding issue. > > I agree with Brent that I am unconvinced we should take off NS from those we > have identified as future value types. Classes we highly suspect should > become value types should retain their NS prefix at this time, as preparation > to avoid the mess that would be to come from reverting, deprecating etc. Just > because we don’t have enough time to get these value types sorted right away > doesn’t mean we should shoot ourselves in the foot by changing things we’ve > already identified as high potential for Value Type Transition. If we > identify other types later on that should move to value semantics, these > strategies would work, but I wonder why deliberately create a headache for > ourselves? > > I am uncertain about the NSCoding proposition as it is not a generic concept > that is platform agnostic. It is a baked in, Objective-C, Apple-only paradigm > that seems to me should retain it’s NS prefix. > >> Is the problem being addressed significant enough to warrant a change to >> Swift? > It’s important to get Swift Foundation and Objective-C Foundation heading in > the right direction, and to provide for more Swiftification in Foundation in > the future, so I think this is significant enough. > >> Does this proposal fit well with the feel and direction of Swift? > Yes and no. I agree with Brent that dropping NS on high-probability value > types is not a wise move, and will slow down value type adoption. It seems > easier to deprecate the name with NS at a later date if it is determined it > must stay a reference type, than it would be trying to go the other way when > we decide to move something to value type. > > >> If you have used other languages or libraries with a similar feature, how do >> you feel that this proposal compares to those? > N/A > >> How much effort did you put into your review? A glance, a quick reading, or >> an in-depth study? > Read through the proposal, and have followed the preceding discussions > regarding value type adoption and the name transition. >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
