Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

I don’t think the API of types have to be bulletproof from the start, but it shouldn’t have core usage limitations based on Objective C. One example would be if I have to deal with NSNumber/NSString/NSArray/NSDictionary to fully use the API, such as NSAttributedString or NSError. The issue is

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

I meant to say that it sounds like a good idea to leave the ’NS’ prefix on types that were auto-translated, and remove it from those that have been rewritten by hand for swift. -Matt > On May 16, 2016, at 21:24, Matt Whiteside wrote: > > This sounds like a good

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

This sounds like a good idea. -Matt > On May 10, 2016, at 03:43, Geordie Jay via swift-evolution > wrote: > > >> Am 10.05.2016 um 12:26 schrieb Haravikk via swift-evolution >> >: >> >> >>> What is your

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

-1 for all the reasons given so far. Foundation is not a Swift API and the NS prefixes help users understand that. Until Foundation gets an API rewrite that makes it feel native in the Swift ecosystem, it should be made very clear that it is a legacy API and not necessary following Swift best

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

We (you) shouldn't remove the NS prefixes from most of the classes in the proposal. I agree with the reasons the other naysayers have given, but I'll try to restate them in my own words. Swift needs a better namespace/import system before these classes should lose the NS prefix. Right now, you

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

On Mon, May 9, 2016, at 03:20 PM, Douglas Gregor via swift-evolution wrote: > * What is your evaluation of the proposal? +1 to enum renaming / hoisting, including turning NSStringEncoding into an enum, but -1 on dropping the NS prefix. I agree with a lot of what the other -1 people have said,

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

Review of proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0086-drop-foundation-ns.md > What is your evaluation of the proposal? I’m +1 on this. I believe that it represents a useful cleanup of the Foundation type naming, and a maturation of the

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> On May 10, 2016, at 12:48 PM, Philippe Hausler via swift-evolution > wrote: > >> >> On May 10, 2016, at 11:11 AM, Ben Rimmington via swift-evolution >> wrote: >> >> >

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> On May 10, 2016, at 11:11 AM, Ben Rimmington via swift-evolution > wrote: > > 0086-drop-foundation-ns.md> > > +1 to dropping the NS prefix; type names are more readable. However: > > * AppKit,

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

+1 to dropping the NS prefix; type names are more readable. However: * AppKit, CoreData, and TextKit will still use the NS prefix. * Prefixed names (in all frameworks) are more "googleable". * Should

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> Am 10.05.2016 um 12:26 schrieb Haravikk via swift-evolution > >: > > >> What is your evaluation of the proposal? > Personally I’m a -1; I’d prefer to see the NS prefix remain on types that > have been translated automatically with

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> Am 10.05.2016 um 12:26 schrieb Haravikk via swift-evolution > >: > > >> What is your evaluation of the proposal? > Personally I’m a -1; I’d prefer to see the NS prefix remain on types that > have been translated automatically with

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> Am 10.05.2016 um 12:26 schrieb Haravikk via swift-evolution > >: > > >> What is your evaluation of the proposal? > Personally I’m a -1; I’d prefer to see the NS prefix remain on types that > have been translated automatically with

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> What is your evaluation of the proposal? Personally I’m a -1; I’d prefer to see the NS prefix remain on types that have been translated automatically with minimal human interaction, in favour of dropping the prefix for types that have received more attention to establish a Swift-ier style,

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

On May 9, 2016, at 7:38 PM, Rod Brown via swift-evolution wrote: > > 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

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> Proposal link: > > 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

Re: [swift-evolution] [Review] SE-0086: Drop NS Prefix in Swift Foundation

> What is your evaluation of the proposal? +1 I already gave my opinion in the original discussion but I’ll summarise it here. I understand the fears that this proposal may inhibit us in the future from making the modifications that Foundation needs to make it feel more Swifty. But I think