[swift-evolution] [Review] SE-0056: Allow trailing closures in `guard` conditions

[Howard Lovatt]

+1 with the same evaluation as Sebastian Hagedorn

On Friday, 1 April 2016, Sebastian Hagedorn via swift-evolution <
swift-evolution at swift.org> wrote:

>
>    - What is your evaluation of the proposal?
>
> +1
>
>
>    - 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.
>
>
>    - If you have used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?
>
> not applicable
>
>
>    - How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?
>
> Followed the mailing list thread and read the proposal.
>
>
> On 01 Apr 2016, at 05:27, Douglas Gregor <dgregor at apple.com
> <javascript:_e(%7B%7D,'cvml','dgregor at apple.com');>> 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
>
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
>
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> or, if you would like to keep your feedback private, directly to the
> review manager. When replying, please try to keep the proposal link at the
> top of the message:
>
> Proposal link:
>
>
> https://github.com/apple/swift-evolution/blob/master/proposals/0056-trailing-closures-in-guard.md
>
> Reply text
>
> Other replies
>
> <https://github.com/apple/swift-evolution#what-goes-into-a-review-1>What
> goes into a review?
>
> The goal of the review process is to improve the proposal under review
> through constructive criticism and, eventually, determine the direction of
> Swift. When writing your review, here are some questions you might want to
> answer in your review:
>
>    - What is your evaluation of the proposal?
>    - Is the problem being addressed significant enough to warrant a
>    change to Swift?
>    - Does this proposal fit well with the feel and direction of Swift?
>    - If you have used other languages or libraries with a similar
>    feature, how do you feel that this proposal compares to those?
>    - How much effort did you put into your review? A glance, a quick
>    reading, or an in-depth study?
>
> More information about the Swift evolution process is available at
>
> https://github.com/apple/swift-evolution/blob/master/process.md
>
> Thank you,
>
> Doug Gregor
>
> Review Manager
> _______________________________________________
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
> <javascript:_e(%7B%7D,'cvml','swift-evolution-announce at swift.org');>
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce
>
>
>

-- 
-- Howard.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160402/3a953a25/attachment.html>