+1, basically the same response as Matt’s. > On Feb 28, 2017, at 1:51 PM, Matthew Johnson via swift-evolution > <[email protected]> wrote: > >> >> What is your evaluation of the proposal? > +1. Checking things off the list of items on the generics manifesto is > always great to see, especially when they allow for improvements in the > standard library. > >> Is the problem being addressed significant enough to warrant a change to >> Swift? > Absolutely. > >> Does this proposal fit well with the feel and direction of Swift? > Very much. > >> If you have used other languages or libraries with a similar feature, how do >> you feel that this proposal compares to those? > N/A > >> How much effort did you put into your review? A glance, a quick reading, or >> an in-depth study? > Quick read, but I have bumped up against this limitation and am really > looking forward to seeing it removed. > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
