Hi everyone, After some discussion, we have a small update to the proposal. The following types will keep their NS prefix:
NSCoding NSSecureCoding NSCoder NSKeyedArchiver NSKeyedUnarchiver The reason is that NSCoding is, at least for the moment, fairly tied to Objective-C (since it is partially implemented with categories on NSObject). The others are not strictly part of that same rule, but they are so tied to NSCoding that I felt it was better to keep them in the same bucket. - Tony > On May 9, 2016, at 3:20 PM, Douglas Gregor via swift-evolution > <swift-evolution@swift.org> wrote: > > Hello Swift community, > > The review of SE-0086 "Drop NS Prefix in Swift Foundation" begins now and > runs through May 16, 2016. The proposal is available here: > > 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> > Reviews are an important part of the Swift evolution process. All reviews > should be sent to the swift-evolution mailing list at > > https://lists.swift.org/mailman/listinfo/swift-evolution > <https://lists.swift.org/mailman/listinfo/swift-evolution> > or, if you would like to keep your feedback private, directly to the review > manager. When replying, please try to keep the proposal link at the top of > the message: > > 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 > > Other replies > > <https://github.com/apple/swift-evolution/blob/master/process.md#what-goes-into-a-review-1>What > goes into a review? > > The goal of the review process is to improve the proposal under review > through constructive criticism and, eventually, determine the direction of > Swift. When writing your review, here are some questions you might want to > answer in your review: > > What is your evaluation of the proposal? > Is the problem being addressed significant enough to warrant a change to > Swift? > Does this proposal fit well with the feel and direction of Swift? > If you have used other languages or libraries with a similar feature, how do > you feel that this proposal compares to those? > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? > More information about the Swift evolution process is available at > > https://github.com/apple/swift-evolution/blob/master/process.md > <https://github.com/apple/swift-evolution/blob/master/process.md> > Thank you, > > -Doug Gregor > > Review Manager > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
