Definitely +1 On Wed, 1 Mar 2017 at 12:59 Haravikk via swift-evolution < [email protected]> wrote:
> On 28 Feb 2017, at 21:40, John McCall via swift-evolution < > [email protected]> wrote: > > > - What is your evaluation of the proposal? > > +1 > > > - Is the problem being addressed significant enough to warrant a > change to Swift? > > Yes. The problem it addresses is an almost daily annoyance when working > with collections! > > > - Does this proposal fit well with the feel and direction of Swift? > > Yes. In fact it removes the need for some very ugly workarounds that are > currently in use within stdlib (and aren't full workarounds anyway). > > > - How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? > > Been following the subject for a while, quick re-read of the latest > proposal. > _______________________________________________ > 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
