Re: [swift-evolution] Switch statement tuple labels

2017-01-01 Thread Tony Allevato via swift-evolution
The "after" example you posted seems to work already in Swift today. Is there something I'm missing? On Sun, Jan 1, 2017 at 7:35 PM David Sweeris via swift-evolution < swift-evolution@swift.org> wrote: > > > Sent from my iPhone > > On Jan 1, 2017, at 19:25, Erica Sadun via swift-evolution < > sw

Re: [swift-evolution] Switch statement tuple labels

2017-01-01 Thread David Sweeris via swift-evolution
Sent from my iPhone > On Jan 1, 2017, at 19:25, Erica Sadun via swift-evolution > wrote: > > Was helping a friend with some code and got inspired. I decided to throw this > on list to see if there's any traction. > > Idea: Introduce optional argument labels to tuples in switch statements >

[swift-evolution] Switch statement tuple labels

2017-01-01 Thread Erica Sadun via swift-evolution
Was helping a friend with some code and got inspired. I decided to throw this on list to see if there's any traction. Idea: Introduce optional argument labels to tuples in switch statements Motivation: Cases can be less readable when pattern matching tuples. Semantically sugared, optional argu

Re: [swift-evolution] [Out of scope][Discussion] Modernize MapKit functions for Swift API Design Guidelines

2017-01-01 Thread Scott Gardner via swift-evolution
Realized that after sending. I'll file a radar. Thanks! Sent from my iPhone > On Jan 1, 2017, at 4:03 PM, Dan Stenmark wrote: > > Swift-evolution is for talking about the core language and its standard > libraries (String, Array, Optional, etc), not high level frameworks like > MapKit. For t

Re: [swift-evolution] [Out of scope][Discussion] Modernize MapKit functions for Swift API Design Guidelines

2017-01-01 Thread Dan Stenmark via swift-evolution
Swift-evolution is for talking about the core language and its standard libraries (String, Array, Optional, etc), not high level frameworks like MapKit. For that, you'll want to file a Radar at http://bugreport.apple.com/ . Dan > On Jan 1, 2017, at 11:02 AM, Scott

[swift-evolution] [Happy New Year !!!!!!!]

2017-01-01 Thread Ted F.A. van Gaalen via swift-evolution
Hey guys & girls, (arbitrary sequence :o) Some of You might perhaps have noticed that it is now 2016++ (oops 2017) So wish each other al good things and events, and the most beautiful things still to find in this mad world (it all depends how we deal with that and has always been that way) Ge

Re: [swift-evolution] [Out of scope][Discussion] Modernize MapKit functions for Swift API Design Guidelines

2017-01-01 Thread Saagar Jha via swift-evolution
MapKit is not part of the Swift standard library; as such, it would probably be better if you used Apple’s Bug Reporter to let them know. Saagar Jha > On Jan 1, 2017, at 11:02 AM, Scott Gardner via swift-evolution > wrote: > > Hello Swift Community, and… > > if Calendar.current.identifier

[swift-evolution] [Out of scope][Discussion] Modernize MapKit functions for Swift API Design Guidelines

2017-01-01 Thread Scott Gardner via swift-evolution
Hello Swift Community, and… if Calendar.current.identifier == .gregorian { print("Happy new year! 🎉") } I would like to propose that the MapKit framework functions be updated to conform to the Swift API Design Guidelines. For example, this is how you would currently determine if the user is