On Thu, 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 > > > - What is your evaluation of the proposal? > > +1 for improving guard. As noted it does leverage an existing inconsistency between guard and if/while/switch (e.g. else) so it isn't really make things that more inconsistent. The use of else in guard exist for good reasons. > > - Is the problem being addressed significant enough to warrant a > change to Swift? > > It is close in my book. > > - Does this proposal fit well with the feel and direction of Swift? > > I think so. I would like to see the modification of if/while/switch as outlined in the alternates section to be more fully evaluated. It would empower those constructs and bring things back into alignment. > > - If you have used other languages or libraries with a similar > feature, how do you feel that this proposal compares to those? > > N/A > > - How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? > > Fully read the proposal and followed the discussion.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
