Re: [swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

on Mon Apr 11 2016, Erica Sadun wrote: > On Apr 11, 2016, at 4:32 PM, Dave Abrahams via swift-evolution > wrote: > > on Mon Apr 11 2016, Russ Bishop wrote: > > Wouldn’t this be the responsibility of UIKit/AppKit teams

Re: [swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

> On Apr 11, 2016, at 4:32 PM, Dave Abrahams via swift-evolution > wrote: > > > on Mon Apr 11 2016, Russ Bishop wrote: > >> Wouldn’t this be the responsibility of UIKit/AppKit teams to provide >> extensions >> that pass the default

Re: [swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

> On Apr 11, 2016, at 4:32 PM, Dave Abrahams via swift-evolution > wrote: > > > on Mon Apr 11 2016, Russ Bishop wrote: > >> Wouldn’t this be the responsibility of UIKit/AppKit teams to provide >> extensions >> that pass the default

Re: [swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

Wouldn’t this be the responsibility of UIKit/AppKit teams to provide extensions that pass the default values? Russ > On Apr 8, 2016, at 10:40 AM, Erica Sadun via swift-evolution > wrote: > > Is there a best way to request default values for common Cocoa and Cocoa

Re: [swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

Thank you Erica, Chris recently noted that UIColor.blackColor() will become UIColor.black() and dismissViewControllerAnimated(true, completion: nil) will become dismissAnimated(true, completion: nil). This latter prompted me to wonder - as the first parameter’s name is flag and first labels

[swift-evolution] Requesting default values for Cocoa/Cocoa Touch APIs

Is there a best way to request default values for common Cocoa and Cocoa Touch APIs? Now that we're moving to Swift, the language supports defaults and omitted parameters but the ObjC APIs do not (yet) supply them. For example, dismissViewControllerAnimated(flag: true, completion: nil) could