> * What is your evaluation of the proposal? Given SE-0121 would get accepted, this proposal does only add small additional value, and might even make code unnecessary complicated.
BUT the nil-coalescing operator (??) really should not allow a non-optional on its left hand side. > * Is the problem being addressed significant enough to warrant a change to > Swift? No, not really once SE-0121 is accepted. > * Does this proposal fit well with the feel and direction of Swift? No, too much boilerplate needed in some cases where the coercion is obvious > * 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? Working with optionals for some while now, and a few minutes thinking through the implications of the proposal. _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
