- 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?
I think the simplicity here is fantastic.
- How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Unfortunately catching up late due to busyness. Though read this current proposal thread and the proposal in full.
My 1 and only question mark revolves around keypath literals.
However, to ensure that it is safe to share key paths, key path literals can only capture values of types that conform to the
Sendableprotocol. This affects uses of subscripts in key paths
I'm wondering why this kind of breaking change could not be avoided? I'd assume that only where keypaths are used within some concurrent context that captured variables would require Sendable. Possibly this was covered in a previous review, and if so, my apologies.
Thanks, and truly awesome proposal overall.