[swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-02-28 Thread John McCall via swift-evolution
Hello Swift community, The review of SE-0157 "Support recursive constraints on associated types" begins now and runs through next Wednesday, March 8, 2017. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0157-recursive-protocol-constraints.md

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-02-28 Thread Matthew Johnson via swift-evolution
> > 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? Abs

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-02-28 Thread Dave Abrahams via swift-evolution
on Tue Feb 28 2017, John McCall wrote: > What is your evaluation of the proposal? +1, duh -- -Dave ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-02-28 Thread John McCall via swift-evolution
> On Feb 28, 2017, at 6:43 PM, Dave Abrahams via swift-evolution > wrote: > on Tue Feb 28 2017, John McCall wrote: > >> What is your evaluation of the proposal? > > +1, duh How much effort would you say that you've put into this review? Very little, a moderate amount, or a great deal? I wi

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-02-28 Thread David Hart via swift-evolution
> On 1 Mar 2017, at 04:00, John McCall via swift-evolution > wrote: > >> On Feb 28, 2017, at 6:43 PM, Dave Abrahams via swift-evolution >> wrote: >> on Tue Feb 28 2017, John McCall wrote: >> >>> What is your evaluation of the proposal? >> >> +1, duh > > How much effort would you say that

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-03-01 Thread Hooman Mehr via swift-evolution
+1, basically the same response as Matt’s. > On Feb 28, 2017, at 1:51 PM, Matthew Johnson via swift-evolution > 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 f

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-03-01 Thread Haravikk via swift-evolution
> On 28 Feb 2017, at 21:40, John McCall via swift-evolution > 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!

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-03-01 Thread Daniel Leping via swift-evolution
Definitely +1 On Wed, 1 Mar 2017 at 12:59 Haravikk via swift-evolution < swift-evolution@swift.org> wrote: > On 28 Feb 2017, at 21:40, John McCall via swift-evolution < > swift-evolution@swift.org> wrote: > > >- What is your evaluation of the proposal? > > +1 > > >- Is the problem being a

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-03-07 Thread T.J. Usiyan via swift-evolution
- What is your evaluation of the proposal? +1 - Is the problem being addressed significant enough to warrant a change to Swift? Yes. Yes. A thousand times, yes. - Does this proposal fit well with the feel and direction of Swift? Yes. - If you have used other languages or librar

Re: [swift-evolution] [Review] SE-0157: Support recursive constraints on associated types

2017-03-08 Thread Jonathan Hull via swift-evolution
> What is your evaluation of the proposal? +1. Much needed improvement. > Is the problem being addressed significant enough to warrant a change to > Swift? Yes, definitely > Does this proposal fit well with the feel and direction of Swift? Yes > If you have used other languages or libraries wit