What is your evaluation of the proposal?
-1
I think the proposal is premature. This review thread reads like a pitch thread.
Is the problem being addressed significant enough to warrant a change to Swift?
The problem is significant enough, but the proposed solution doesn't seem right.
It hasn't been discussed in this thread yet, but having synthesised Codable requirement can greatly ease the encoding/decoding arbitrarily nested data with indirect/recursive enums.
Does this proposal fit well with the feel and direction of Swift?
No.
Swift values correctness in default behaviour. It's not convincing that the proposed solution is the correct serialisation/deserialisation strategy for enums.
The proposed solution is not general enough, so it applies to only some enums. It's also looks unlikely the feature, if accepted, can be easily expanded to cover more kind of enums.
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I haven't used anything with a similar feature.
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
I didn't participat the pitch tread(s). I read the proposal in full, read all posts up-thread, and posted a few suggestions.