[swift-evolution] Dropping NS Prefix in Foundation
rodney.brown6 at icloud.com
Fri May 6 17:34:40 CDT 2016
I am definitely +1 to this proposal direction
I was in the crowd thinking "don't drop the NS on types that should be value types" but I think you make fair points that there can be planned optimizations in the future, and we should focus on getting a good set of naming rules in place. You make decent rules about how to migrate going forward.
I'm definitely in favor of the hoisted types, enum updates etc.
I found it interesting that NSOrderedSet has been left out of this proposal. Is there any reason for this? I only thought about it in regard to the previous mention a few days ago heh.
Thanks Tony for pushing this forward.
> On 7 May 2016, at 6:52 AM, Tony Parker via swift-evolution <swift-evolution at swift.org> wrote:
> Hi everyone,
> Thanks to all of you for your feedback on SE-0069 (Foundation Value Types). I’m back again with more information on another part of our plan to integrate Foundation API into Swift: dropping the NS prefix.
> When we originally proposed this as part of the API guidelines document (SE-0023, https://github.com/apple/swift-evolution/blob/master/proposals/0023-api-guidelines.md), we took a very broad approach to which classes would drop their prefix. This time, we’ve narrowed the scope considerably, plus taken advantage of the ability to nest types inside classes to further reduce the possibility of introducing conflicting names.
> I’ve written up a draft of the proposal, which includes an extensive section on motivation plus a list of changes. Please take a look and let me know what you think. We’ll start a formal review period soon.
> Thanks again for your help,
> - Tony
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution