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 me as the review manager via the forum messaging feature. When contacting the review manager directly, please put "SE-0399" in the subject line.
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
I'm trying out the latest snapshot and it seems like the implementation still uses the original syntax from 0393's future directions (e.g. repeat print(each tuple.element) instead of repeat print(each tuple)). The proposal says the implementation is on main so I assume it hasn't made it into a snapshot yet or the .element syntax is just being used until this is accepted? (I grabbed the latest snapshot toolchain this morning).
In terms of the proposal itself, I think it's really clean! I wasn't a fan of the each tuple.element syntax mentioned in 0393; treating abstract tuples the same as value packs makes so much more sense :)
Apologies, the implementation note should probably say something more like "partial" given that, as you noted, it still is with the earlier .element syntax. The work to drop that syntax is underway but not yet complete. Glad to hear that this will be useful for you and the specifics about that!