Re: [go-nuts] Signature Switch - third path to Go generics

2020-12-31 Thread Wojciech S. Czarnecki
Dnia 2020-12-31, o godz. 13:15:00 "K. Alex Mills" napisaƂ(a): > At a glance, this feels to me like it is more complicated than the current > generics proposal. That said, it also seems very original so I have to give > credit there. It is just the other kind, as I see it. You know, it was born j

Re: [go-nuts] Signature Switch - third path to Go generics

2020-12-31 Thread Ian Lance Taylor
On Thu, Dec 31, 2020 at 10:37 AM Wojciech S. Czarnecki wrote: > > I regard current Team's proposal a way better than the first iteration. But - > while I see a need for generic way to write common code, I also share > concerns about readability and future abuse of the materialized Go generics > be

Re: [go-nuts] Signature Switch - third path to Go generics

2020-12-31 Thread K. Alex Mills
At a glance, this feels to me like it is more complicated than the current generics proposal. That said, it also seems very original so I have to give credit there. This proposal seems to put the responsibility for monomorphizing generic code onto the programmer. I'm not sure why it would be simpl

[go-nuts] Signature Switch - third path to Go generics

2020-12-31 Thread Wojciech S. Czarnecki
I regard current Team's proposal a way better than the first iteration. But - while I see a need for generic way to write common code, I also share concerns about readability and future abuse of the materialized Go generics being similar to "the other languages". I consciously did not patricipate i