Hi Chris, Don’t you think the suggestion is better? I’m happy to formula it in terms of an E(BNF) grammar if you like. Is this published/available anywhere, for the current version of Swift?
Thanks. > On 21 Dec 2015, at 19:22, Chris Lattner <[email protected]> wrote: > >> >> On Dec 21, 2015, at 11:20 AM, Alexander Regueiro via swift-evolution >> <[email protected]> wrote: >> >> Does anyone not like the current syntax for this? >> >> I would propose changing it from: >> >> { (param_list) -> return_type in … } >> >> to something cleaner like: >> >> (param_list) -> return_type => { … } >> >> where I’m not so bothered about the `=>` separator (could be `:`, `,`, or >> indeed `in`). >> >> The braces being around the type specifier as well as function body rather >> bothers me. Surely it would be more consistent just to have the braces >> around the function body, and then the type specifier preceding this? > > Hi Alexander, > > We’re open in principle to replacing closure syntax with something better, > but A) it needs to be actually better, and B) it needs to fit with the swift > grammar. If you’re interested in pushing forward in this area, please > familiarize yourself with the structure of the grammar and propose what > you’re thinking in terms of a diff to it. Thanks, > > -Chris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
