<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><b class="">What is your evaluation of the proposal?</b><div class="">A big +1<br class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></div><div class=""><b class="">Is the problem being addressed significant enough to warrant a change to Swift?</b></div><div class="">Yes. This makes it much more natural to read methods and functions with generics. This also makes it more predictable to find where the method signature is without having to weed through a bunch of generic constraints.<br class=""><br class=""></div><div class=""><b class="">Does this proposal fit well with the feel and direction of Swift?</b></div><div class="">Most definitely. Feels more natural and consistent with other uses of `where`<br class=""><br class=""></div><div class=""><b class="">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</b></div><div class=""><b class="">N/A<br class=""></b><br class=""></div><div class=""><b class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b></div></div><div class="">I’ve followed the evo thread since the beginning</div></body></html>