The second review of SE-0279 — Multiple Trailing Closures begins now and runs through April 24, 2020.
This is the second review, with a modified proposal. The core team has considered the feedback from the first review and believes that:
- the underlying motivation for the proposal does merit a change to the language to better accommodate multiple trailing closures;
- the concerns around the original proposed syntax warranted a rethink of the proposed solution.
The proposal authors have a revised proposal that aims to address some of those concerns.
A diff between the previous and latest proposal can be found here.
Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to the review manager (via email or direct message in the Swift forums).
What goes into a review of a proposal?
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift.
When reviewing a proposal, here are some questions to consider:
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?