> * What is your evaluation of the proposal? Very welcome change that should reduce unexpected behavior in some cases.
> * Is the problem being addressed significant enough to warrant a change to > Swift? Yes, as it could avoid programming mistakes. > * Does this proposal fit well with the feel and direction of Swift? Definitely, the more obvious the code reads the better. > * 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? I experienced Swifts behavior in this case since Swift 1.0, and it always felt wrong. _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
