> * What is your evaluation of the proposal? +1 The new API conventions for member references (especially enums) seem broken without this proposal IMHO.
> * Is the problem being addressed significant enough to warrant a change > to Swift? I think it is paramount. > * Does this proposal fit well with the feel and direction of Swift? It does. > * If you have you used other languages or libraries with a similar > feature, how do you feel that this proposal compares to those? I can’t think of another language that has lowercase enums so the keyword conflicts did not exist. > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? A good read. > > More information about the Swift evolution process is available at > > https://github.com/apple/swift-evolution/blob/master/process.md > > Thank you, > > -Chris Lattner > 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
