> What is your evaluation of the proposal? +1 to the idea. Disappointing that we don’t seem to be able to add this to @objc enums. Could we come up with some kind of workaround for this?
> Is the problem being addressed significant enough to warrant a change to > Swift? Yes, this is a common problem where I constantly write all case static properties, and where I use the count. To be honest, for such a robust system, I found it a glaring omission. > Does this proposal fit well with the feel and direction of Swift? Yes, the way the proposed solution is designed seems to work well. > If you have used other languages or libraries with a similar feature, how do > you feel that this proposal compares to those? I’ve done a lot of hacked enum “allCases” implementations in Swift, and we really didn’t have this power in the other languages I’ve used. > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? Quick reading. Sent from my iPad > On 9 Jan 2018, at 6:02 am, Douglas Gregor via swift-evolution > <swift-evolution@swift.org> wrote: > > Hello Swift community, > > The review of SE-0194 "Derived Collection of Enum Cases" begins now and runs > through January 11, 2018. The proposal is available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0194-derived-collection-of-enum-cases.md > Reviews are an important part of the Swift evolution process. All reviews > should be sent to the swift-evolution mailing list at > > https://lists.swift.org/mailman/listinfo/swift-evolution > or, if you would like to keep your feedback private, directly to the review > manager. When replying, please try to keep the proposal link at the top of > the message: > > Proposal link: > > https://github.com/apple/swift-evolution/blob/master/proposals/0194-derived-collection-of-enum-cases.md > Reply text > Other replies > 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 > > https://github.com/apple/swift-evolution/blob/master/process.md > Thank you, > > -Doug Gregor > > Review Manager > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
