Re: [swift-evolution] [Pitch] Remove associated type inference

I’m inclined to say -1, for reasons that’ve already been mentioned, but can anyone elaborate on “a drastically different architecture to the type checker”? - Dave Sweeris > On May 25, 2016, at 4:43 PM, David Hart via swift-evolution > wrote: > > Here’s a pitch for

Re: [swift-evolution] [Pitch] Remove associated type inference

On Thu, May 26, 2016 at 12:47 PM, L. Mihalkovic via swift-evolution < swift-evolution@swift.org> wrote: > > > On May 25, 2016, at 11:43 PM, David Hart via swift-evolution < > swift-evolution@swift.org> wrote: > > Here’s a pitch for removing associated type inference as per the Generics >

Re: [swift-evolution] [Pitch] Remove associated type inference

ntations... a very narro part of the language. And considering the new type aliasing capabilities, one that we may need even less than before. > From: Matthew Johnson via swift-evolution > Sent: ‎25/‎05/‎2016 07:06 PM > To: David Hart > Cc: Swift-evolution > Subject: Re: [swift-evolution] [P

Re: [swift-evolution] [Pitch] Remove associated type inference

On Thu, May 26, 2016, at 02:26 AM, David Hart via swift-evolution wrote: > I believe it also helps readability. Associated type are part of the > declaration and I think it's worth pursuing better readability than > programmer friendliness at the declaration. When reading a type > declaration that

Re: [swift-evolution] [Pitch] Remove associated type inference

Sent from my iPad > On May 26, 2016, at 1:21 AM, David Hart via swift-evolution > wrote: > > We could have the generic type parameter always shadow the associated type. I believe there has been talk of automatically introducing an associated type corresponding to

Re: [swift-evolution] [Pitch] Remove associated type inference

Sent: ‎25/‎05/‎2016 07:06 PM >> To: David Hart >> Cc: Swift-evolution >> Subject: Re: [swift-evolution] [Pitch] Remove associated type inference >> >> I agree that if we’re going to do it we should probably do it in Swift 3. >> But it is a very convenient

Re: [swift-evolution] [Pitch] Remove associated type inference

We could have the generic type parameter always shadow the associated type. > On 26 May 2016, at 06:08, Patrick Smith wrote: > > While this has been a handy feature, I don’t mind making things more > explicit, as I think it helps communication. Sometimes clarity that helps

Re: [swift-evolution] [Pitch] Remove associated type inference

While this has been a handy feature, I don’t mind making things more explicit, as I think it helps communication. Sometimes clarity that helps the compiler will also help the reader. It’s only really convenient when writing. I would be happy with this change as long as the issue with same named

Re: [swift-evolution] [Pitch] Remove associated type inference

wareness in the language - not less! >>>> >>>> l8r >>>> Sean >>>> >>>> Sent from my iPad >>>> >>>> On May 25, 2016, at 5:37 PM, Leonardo Pessoa via swift-evolution >>>> <swift-evolution@swift.org <mail

Re: [swift-evolution] [Pitch] Remove associated type inference

Pessoa via swift-evolution >>>>>> <swift-evolution@swift.org> wrote: >>>>>> >>>>>> -1. I don't really see how this is a bad thing and why it has to change. >>>>>> To me this is one of the best features of the language and

Re: [swift-evolution] [Pitch] Remove associated type inference

've been through some situations it was totally obvious the expected type >>> of a variable and the compiler couldn't infer it) not less. >>> >>> From: Matthew Johnson via swift-evolution <mailto:swift-evolution@swift.org> >>> Sent: ‎25/‎05/‎2016

Re: [swift-evolution] [Pitch] Remove associated type inference

n't infer it) not less. >> >> -- >> From: Matthew Johnson via swift-evolution <swift-evolution@swift.org> >> Sent: ‎25/‎05/‎2016 07:06 PM >> To: David Hart <da...@hartbit.com> >> Cc: Swift-evolution <swift-evolution@

Re: [swift-evolution] [Pitch] Remove associated type inference

r it) not less. > > -- > From: Matthew Johnson via swift-evolution <swift-evolution@swift.org> > Sent: ‎25/‎05/‎2016 07:06 PM > To: David Hart <da...@hartbit.com> > Cc: Swift-evolution <swift-evolution@swift.org> > Subject: Re: [swi

Re: [swift-evolution] [Pitch] Remove associated type inference

. -Original Message- From: "Matthew Johnson via swift-evolution" <swift-evolution@swift.org> Sent: ‎25/‎05/‎2016 07:06 PM To: "David Hart" <da...@hartbit.com> Cc: "Swift-evolution" <swift-evolution@swift.org> Subject: Re: [swift-evolution] [

Re: [swift-evolution] [Pitch] Remove associated type inference

Sent from my iPad > On May 25, 2016, at 6:11 PM, Dmitri Gribenko via swift-evolution > wrote: > >> On Wed, May 25, 2016 at 3:42 PM, Leonardo Pessoa wrote: >>> On Wednesday, 25 May 2016, Dmitri Gribenko via swift-evolution >>>

Re: [swift-evolution] [Pitch] Remove associated type inference

I'm not quite sure I follow you. I am suggesting only removing it for associated type inference, where we fairly rarely benefit from it compared to general type inference. > On 26 May 2016, at 00:42, Leonardo Pessoa wrote: > > If the issue is easing the work of the

Re: [swift-evolution] [Pitch] Remove associated type inference

On Wed, May 25, 2016 at 3:42 PM, Leonardo Pessoa wrote: > On Wednesday, 25 May 2016, Dmitri Gribenko via swift-evolution < > swift-evolution@swift.org> wrote: > >> On Wed, May 25, 2016 at 2:52 PM, David Hart wrote: >> > >> >> On 25 May 2016, at 23:47,

Re: [swift-evolution] [Pitch] Remove associated type inference

On Wednesday, 25 May 2016, Dmitri Gribenko via swift-evolution < swift-evolution@swift.org> wrote: > On Wed, May 25, 2016 at 2:52 PM, David Hart > wrote: > > > >> On 25 May 2016, at 23:47, Dmitri Gribenko > wrote: > >> > >>

Re: [swift-evolution] [Pitch] Remove associated type inference

I’m in favour if it simplifies the type checker, and also I kind of prefer this as I’d rather overriding/implementing methods consistently used associated types. As long as the warning is clear it shouldn’t introduce many problems, and Swift 3 is going to be a transition for most as it is

Re: [swift-evolution] [Pitch] Remove associated type inference

On Wed, May 25, 2016 at 2:52 PM, David Hart wrote: > >> On 25 May 2016, at 23:47, Dmitri Gribenko wrote: >> >> On Wed, May 25, 2016 at 2:43 PM, David Hart via swift-evolution >> wrote: >>> Impact on Existing Code >>> >>> This is

Re: [swift-evolution] [Pitch] Remove associated type inference

I agree that if we’re going to do it we should probably do it in Swift 3. But it is a very convenient and useful feature that significantly lowers the bar of conforming to protocols with associated types (in many cases you can just implement the required members without thinking about the

Re: [swift-evolution] [Pitch] Remove associated type inference

> On 25 May 2016, at 23:47, Dmitri Gribenko wrote: > > On Wed, May 25, 2016 at 2:43 PM, David Hart via swift-evolution > wrote: >> Impact on Existing Code >> >> This is a breaking change that will require conforming types which relied on >> the

Re: [swift-evolution] [Pitch] Remove associated type inference

On Wed, May 25, 2016 at 2:43 PM, David Hart via swift-evolution wrote: > Impact on Existing Code > > This is a breaking change that will require conforming types which relied on > the inference, including in the Standard Library, to explicitly declare > associated

[swift-evolution] [Pitch] Remove associated type inference

Here’s a pitch for removing associated type inference as per the Generics Manifesto. If we want to do it, we’d better do it before Swift 3: Remove associated type inference Proposal: SE-