[swift-evolution] [swift-evolution-announce] [Review] SE-0155: Normalize Enum Case Representation
matthew at anandabits.com
Sat Feb 18 10:47:27 CST 2017
> • What is your evaluation of the proposal?
+1. I am extremely confident that this is the right direction to go in.
I really like Brent’s idea for allowing us to distinguish the parameter label from what he calls the “internal name”.
In the value subtyping manifesto I recently posted I showed how we can assign a unique type to each enum case which is a subtype of the enum itself. The “internal name” Brent mentions would be the name of the stored property holding the value if that idea were introduced in the future. It has value beyond just documentation and autocompletion.
> • Is the problem being addressed significant enough to warrant a change to Swift?
Yes. Several years of experience with Swift are showing that there are many reasons for this to change.
> • Does this proposal fit well with the feel and direction of Swift?
Very much so.
> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I have not. The approach Swift takes to compound names is unique in my experience and is a very nice design.
> • 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 https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>
> Thank you,
> John McCall
> Review Manager
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution