Re: [swift-evolution] Notification.Name

2016-07-05 Thread Tony Parker via swift-evolution
Hi Brent, In general, I agree with your idea that the scope of the name of these things is with the type it’s used for. The type of it is of course Notification.Name. One thing we did in the short term to make this feature even remotely possible was to add an importer rule: global const

Re: [swift-evolution] Notification.Name

2016-06-30 Thread Michael Ilseman via swift-evolution
> On Jun 30, 2016, at 9:10 AM, Ben Rimmington wrote: > > [Cc: Michael Ilseman] > >> On 30 Jun 2016, at 03:13, Brent Royal-Gordon via swift-evolution >> wrote: >> >> Not 100% sure this belongs here, but I'll bite. >> >> The new

[swift-evolution] Notification.Name

2016-06-29 Thread Brent Royal-Gordon via swift-evolution
Not 100% sure this belongs here, but I'll bite. The new `Notification.Name` type is a beautiful application of SE-0033 "Import Objective-C Constants as Swift Types"[1] which removes a lot of boilerplate. However, I think it puts the resulting constants in the wrong place. They all get piled