What is your evaluation of the proposal?
+1
Is the problem being addressed significant enough to warrant a change to Swift?
I actually do not know. This introduces a lot of more complexity to the language specially with the introduction of $ auto synthesized storage variable. This brings me back when I was learning obj-c and was totally confused about synthesized getters and setters.
I think the name doesn't fit the feature as proposed. The only part that would fit the name is the "Delegating to an existing propety" which is not part of the proposal but if it was, would we need $ ?
https://github.com/apple/swift-evolution/blob/master/proposals/0258-property-delegates.md#delegating-to-an-existing-property
Does this proposal fit well with the feel and direction of Swift?
The latest swift proposal have been trying to introduce a lot of features that would make the language more complex (some aka opaque) and I feel that this one is also in the same complexity area.
It would seem to me that swift its trying really hard to be like rust but if I wanted swift to be like rust I would just go use rust. I've been using golang and It reminds me of swift a lot but lately i feel that it will become so complicated that I might as well learn rust for another project. I have a dream of using Swift outside of iOS.
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?
Read both pitches