> > • What is your evaluation of the proposal? +1
> • Is the problem being addressed significant enough to warrant a change > to Swift? Yes. > • Does this proposal fit well with the feel and direction of Swift? Yes. > • If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? I really don't like language compilers/interpreters that do not warn when a return value hasn't been consumed. It is one of the few aspects of Ruby that I dislike, and it causes no end of frustration. However, this enforces a policy while allowing a opt-out behavior, which is a plus. Either way, the developer was forced to consider the return value. > • How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Quick read. _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
