Sent from my iPad
> On Jun 14, 2017, at 11:01 PM, Chris Lattner via swift-evolution > <swift-evolution@swift.org> wrote: > > >> On Jun 12, 2017, at 10:07 PM, Paul Cantrell <cantr...@pobox.com> wrote: >> >> What’s the status of this Chris’s double parens idea below? It garnered some >> positive responses, but the discussion seems to have fizzled out. Is there >> something needed to help nudge this along? >> >> What’s the likelihood of getting this fixed before Swift 4 goes live, and >> the great wave of readability regressions hits? > > We discussed this in the core team meeting today. Consensus seems to be that > a change needs to be made to regain syntactic convenience here. Discussion > was leaning towards allowing (at least) the parenthesized form, but more > discussion is needed. > > > One (tangential) thing that came up is that tuple element names in tuple > *patterns* should probably be deprecated and removed at some point. Without > looking, what variables does this declare?: > > let (a : Int, b : Float) = foo() Another option would be to require let to appear next to each name binding instead of allowing a single let for the whole pattern. I personally find that much more clear despite it being a little bit more verbose. > > ? > > -Chris > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
