> • What is your evaluation of the proposal? Great idea
> • Is the problem being addressed significant enough to warrant a change > to Swift? Yes I think so, currently the declaration line is very cluttered with lots of noise up front that hides what the line actually does. This proposal removes some of that noise. > • Does this proposal fit well with the feel and direction of Swift? Yes, Swift is clutter free and tries to pick as the default the most common case > • If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? I have used languages with the current Swift behaviour of having to explicitly initiate the warning and they like Swift tended to be a pain. Either the declaration got cluttered or the annotation was omitted. I have used products like lint for C and appreciated that it automatically warned about unused returned values. > • How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Have followed along on Swift Evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
