Re: [swift-evolution] Remove prefixes from all Apple frameworks

Not only with your own code. There is so many Apple Framework, I’m pretty sure it won’t be difficult to find conflicting class name. > Le 31 mars 2017 à 08:02, Rien via swift-evolution > a écrit : > > The problem with unprefixed names is name clashes with my own

Re: [swift-evolution] Remove prefixes from all Apple frameworks

The problem with unprefixed names is name clashes with my own code. Not often, but often enough. Then you have to invent your owm prefixes. Besides, NS… and UI… make it much, MUCH more convenient to google… Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github:

Re: [swift-evolution] Remove prefixes from all Apple frameworks

Loud and clear! :-) I am, however, very interested in the thoughts of the Swift evolution community for this idea. – Louis D'hauwe > On 30 Mar 2017, at 23:28, Joe Groff wrote: > >> >> On Mar 30, 2017, at 2:03 PM, Louis D'hauwe via swift-evolution >>

Re: [swift-evolution] Remove prefixes from all Apple frameworks

> On Mar 30, 2017, at 2:03 PM, Louis D'hauwe via swift-evolution > wrote: > > Apple frameworks contain prefixes, carried over from Objective-C. > These exist to prevent class and method name collisions. > > Mattt Thompson has a great article about this, containing

Re: [swift-evolution] Remove prefixes from all Apple frameworks

By an alias what I really meant was some kind of a macro like NS_SWIFT_NAME for types and the module name. --  Adrian Zubarev Sent with Airmail Am 30. März 2017 um 23:19:51, Louis D'hauwe (louisdha...@silverfox.be) schrieb: Aliases would be one step towards my vision, but long term I'd like

Re: [swift-evolution] Remove prefixes from all Apple frameworks

Aliases would be one step towards my vision, but long term I'd like to see a class like "UIViewController" to be imported as "ViewController". > On 30 Mar 2017, at 23:17, Adrian Zubarev > wrote: > > Typo: I actually meant type- and module-alias. > > > > >

Re: [swift-evolution] Remove prefixes from all Apple frameworks

Typo: I actually meant type- and module-alias. --  Adrian Zubarev Sent with Airmail Am 30. März 2017 um 23:16:14, Adrian Zubarev (adrian.zuba...@devandartist.com) schrieb: Something like a type- and type-alias when importing from Obj-C to Swift? That would be reasonable, I’d guess. -- 

Re: [swift-evolution] Remove prefixes from all Apple frameworks

Something like a type- and type-alias when importing from Obj-C to Swift? That would be reasonable, I’d guess. --  Adrian Zubarev Sent with Airmail Am 30. März 2017 um 23:12:30, Louis D'hauwe (louisdha...@silverfox.be) schrieb: I disagree, my proposal is not to rename Apple frameworks.  It

Re: [swift-evolution] Remove prefixes from all Apple frameworks

I disagree, my proposal is not to rename Apple frameworks. It is to improve the importing of Objective-C designed frameworks to remove the unnecessary prefixes. – Louis D'hauwe > On 30 Mar 2017, at 23:07, Adrian Zubarev > wrote: > > The issue is, this has

Re: [swift-evolution] Remove prefixes from all Apple frameworks

Oh yeah; and they might want to reserve unprefixed names for native Swift interfaces, similar to what happened to Foundation. Maybe they already did. We’ll have to wait until WWDC for the next major version of the SDKs. - Karl > On 30 Mar 2017, at 23:07, Adrian Zubarev via swift-evolution >

Re: [swift-evolution] Remove prefixes from all Apple frameworks

The issue is, this has nothing to do with swift evolution. You could file a bug report for the Apple frameworks, but I doubt something this huge will make it through. --  Adrian Zubarev Sent with Airmail Am 30. März 2017 um 23:03:52, Louis D'hauwe via swift-evolution

Re: [swift-evolution] Remove prefixes from all Apple frameworks

+ Int.max - Karl ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

[swift-evolution] Remove prefixes from all Apple frameworks

Apple frameworks contain prefixes, carried over from Objective-C. These exist to prevent class and method name collisions. Mattt Thompson has a great article about this, containing the following brilliant excerpt: "Namespacing is the preeminent bugbear of Objective-C. A cosmetic quirk with