[swift-evolution] Fixing Apple Framework APIs in regard to the Swift Design Guidelines

[Chris Lattner]

> On Jun 18, 2016, at 10:14 PM, Brent Royal-Gordon <brent at architechies.com> wrote:
> 
>> swift-evolution isn’t the right process for proposing changes to Apple frameworks, but you raise good points, and I really value the feedback.  
>> 
>> If you file a radar with bugreporter.apple.com and let us know the radar #, we will be happy to escalate this with the team in question.  Thank you!
> 
> Oh, I've got a list of radars to file that's as long as my arm.
> 
> To clarify: Radar is the best place to file imperfect APIs in random frameworks. Where is the best place to bring up:
> 
> 1. Migrator issues?

swift-users or swift-dev (if you’re trying to improve the migrator and have questions about it).

> 
> 2. Foundation issues (with the new value types)?
> 3. Foundation issues caused by evolution-proposed features behaving in ways that are problematic for certain uses Foundation puts them to? (Specifically, symbols marked with NSNotificationName get imported as constants on Notification.Name by default due to the design of SE-0033; you'd probably prefer they be prefix-matched and inserted into the type they belong to.)

I’d ask the folks on swift-corelibs-dev what they prefer.

-Chris