> On Mar 31, 2016, at 8:27 PM, Douglas Gregor via swift-evolution > <[email protected]> wrote: > > Hello Swift community, > > The review of SE-0056 "Allow trailing closures in `guard` conditions" begins > now and runs through April 5, 2016. The proposal is available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0056-trailing-closures-in-guard.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0056-trailing-closures-in-guard.md> > What is your evaluation of the proposal? +1 - I’m in favor of it.
> Is the problem being addressed significant enough to warrant a change to > Swift? Yes > Does this proposal fit well with the feel and direction of Swift? Yes. The point of trailing closure syntax is to allow user-defined functions to look like natural control flow statements. This is especially true for guard and the omission of the capability is an obvious oversight. The arguments against it seem to be arguments against trailing closure syntax entirely which is a separate issue from this proposal. So long as trailing closure syntax exists it should be usable in a guard statement. > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? Reading the proposal and the various threads, plus some thinking time. Russ
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
