Re: [swift-evolution] Some clarity lost from the great renaming

I wrote a script to find “needless words” in our function names and made a similar discovery. If “doXWithY(_ y: Y)” gets renamed to “doX(with y: Y)” and Y happened to be a enum or have static members, at use site it become a little awkward. Following Brandon’s first example: 1. “normal” is an

Re: [swift-evolution] Some clarity lost from the great renaming

on Tue Oct 18 2016, Hooman Mehr wrote: > Is changing the mapping of Cocoa API considered a source breaking > change or can we report such incidents as bugs if we think they don’t > match API guidelines? You can report them as bugs even if it would be source breaking. > > >> On Oct 18, 2016,

Re: [swift-evolution] Some clarity lost from the great renaming

Sorry! I was unsure if this would be a breaking change so thought I would seek feedback. It sounds like I'm not the only one bothered by this so I will file a radar Brandon Sent from my iPad > On Oct 18, 2016, at 9:43 PM, Dave Abrahams via swift-evolution >

Re: [swift-evolution] Some clarity lost from the great renaming

They can always add the new mapping, and leave the old one there but deprecate it. Charles > On Oct 18, 2016, at 8:51 PM, Hooman Mehr via swift-evolution > wrote: > > Is changing the mapping of Cocoa API considered a source breaking change or > can we report such

Re: [swift-evolution] Some clarity lost from the great renaming

Agree on this particular case being unintuitive. I've come across a number of such cases in Swift 3 but never really put too much thought into them. Maybe you could just use for: UIControlState.normal until a resolution for this is found (if there is one). On Tue, Oct 18, 2016 at 10:32 PM Dennis

Re: [swift-evolution] Some clarity lost from the great renaming

I think if it's one example like in this instance then a compiler directive to specify mapping if one does not already exist would be a more prudent option than changing the entire mapping. On Tue, Oct 18, 2016 at 9:51 PM Hooman Mehr via swift-evolution < swift-evolution@swift.org> wrote: > Is

Re: [swift-evolution] Some clarity lost from the great renaming

Is changing the mapping of Cocoa API considered a source breaking change or can we report such incidents as bugs if we think they don’t match API guidelines? > On Oct 18, 2016, at 6:43 PM, Dave Abrahams via swift-evolution > wrote: > > > on Tue Oct 18 2016, Brandon

Re: [swift-evolution] Some clarity lost from the great renaming

on Tue Oct 18 2016, Brandon Knope wrote: > I meant to bring this up a bit ago but just came across it again. > > I find this to not read properly: > > button.setTitle("Test", for: .normal) //for normal what? > > The for argument is really only clear in meaning when

[swift-evolution] Some clarity lost from the great renaming

I meant to bring this up a bit ago but just came across it again. I find this to not read properly: button.setTitle("Test", for: .normal) //for normal what? The for argument is really only clear in meaning when you are typing it out and see that it is a UIControlState type. While reading it