Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jul 6, 2016, at 10:43 AM, Jordan Rose wrote: > >> >> On Jul 1, 2016, at 15:53, Russ Bishop > > wrote: >> >> >>> On Jun 30, 2016, at 4:23 PM, Jordan Rose via swift-evolution >>>

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jul 1, 2016, at 15:53, Russ Bishop wrote: > > >> On Jun 30, 2016, at 4:23 PM, Jordan Rose via swift-evolution >> > wrote: >> >> [Proposal: >>

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jun 30, 2016, at 4:23 PM, Jordan Rose via swift-evolution > wrote: > > [Proposal: > https://github.com/apple/swift-evolution/blob/master/proposals/0108-remove-assoctype-inference.md > >

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jun 29, 2016, at 10:55 PM, Douglas Gregor wrote: > > You're talking about recursive protocol constraints (which would help > collapse some of the underscored protocols) and where clauses on associated > types in particular? I'm also talking about "caveman inference" if

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

* What is your evaluation of the proposal? + 1 * Is the problem being addressed significant enough to warrant a change to Swift? Yes. When inference goes wrong it is frustrating and difficult to puzzle out. * Does this proposal fit well with the feel and direction of Swift?

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

[Proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0108-remove-assoctype-inference.md ] I’m pretty concerned about completely removing this feature. Yes, it’s a

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jun 29, 2016, at 4:38 PM, Brent Royal-Gordon via swift-evolution > wrote: > >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0108-remove-assoctype-inference.md > >> * What is your evaluation of the proposal? > > I don't think the

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> On Jun 29, 2016, at 4:38 PM, Brent Royal-Gordon via swift-evolution > wrote: > > Additionally, I believe the other un-defaulted associated types we'd like to > infer if we can—`Collection.Index`, `Sequence.Iterator`, and > `IteratorProtocol.Element`—could all be

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> > * What is your evaluation of the proposal? I’m going to stay neutral. The motivation is implementation focused and I am not qualified to adequately assess it. It does sound like it might be necessary to do this (at least temporarily) in order to facilitate evolution of other

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0108: Remove associated type inference

> > https://github.com/apple/swift-evolution/blob/master/proposals/0108-remove-assoctype-inference.md > * What is your evaluation of the proposal? I don't think the time is right. I've been reading the code for Sequence, Collection, and the various protocols that they use (I