On Tuesday, June 21, 2016 at 2:56:01 PM UTC-4, Axel Wagner wrote: The issue
is, that a "KeyValuePair" (no matter if you implemented it via generics
or like you mention via interfaces) i
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscri
On 21 Jun 2016, at 19:55, 'Axel Wagner' via golang-nuts
wrote:
> The issue is, that a "KeyValuePair" (no matter if you implemented it
> via generics or like you mention via interfaces) is a fundamentally useless
> type and generics encourage people to add useless types. A "KeyValuePair V>" is
I guess that's for diplomatic reasons. If you watch talks of core
contributors then I believe you'll know what I mean :)
On Tue, Jun 21, 2016 at 5:15 AM, Rodrigo Kochenburger wrote:
> Micky, I'm not sure where you're quoting from but they never said it's never
> gonna happen.
>
> From the FAQ: "G
Micky, I'm not sure where you're quoting from but they never said it's
never gonna happen.
>From the FAQ: "Generics may well be added at some point." and "This remains
an open issue".
https://golang.org/doc/faq#generics
On Mon, Jun 20, 2016 at 4:54 PM Micky wrote:
> It's never going to happen
It's never going to happen! To quote the powers-to-be, "The language is done".
Good luck!
On Wed, Jun 15, 2016 at 6:04 AM, xingtao zhao wrote:
> Here is my proposal for generic in go:
> https://docs.google.com/document/d/1nO7D15c2B3eq2kF62C0yUs_UgpkyPL2zHhMAmlq1l98/edit?usp=sharing
>
> Many parts
I read your proposals now. My proposal is very similar to your proposal of
type parameter - in fact, they are almost identical. But in my proposal, I
am not going that far as in your proposal. I did not include the operators,
thus all generic functions can only access the unknown type through
i
On Tue, Jun 14, 2016 at 6:04 PM, xingtao zhao wrote:
> Here is my proposal for generic in go:
> https://docs.google.com/document/d/1nO7D15c2B3eq2kF62C0yUs_UgpkyPL2zHhMAmlq1l98/edit?usp=sharing
>
> Many parts has not been finished, and just initial thoughts. In the
> proposal, I want to keep back c
Here is my proposal for generic in go:
https://docs.google.com/document/d/1nO7D15c2B3eq2kF62C0yUs_UgpkyPL2zHhMAmlq1l98/edit?usp=sharing
Many parts has not been finished, and just initial thoughts. In the
proposal, I want to keep back compatibility. And I try to add the
orthogonal feature only a
