[RabbitmqGuy]

As a person who uses Go i don't need day by day updates to know that the Go team is working hard on generics. I trust that they are & indeed they are.

> now one year old with little visible progress, no updates since August on public git.

This is untrue.

In January this year the Go team wrote[1]; "Module support is in good shape and getting better with each day, and we are also making progress on the generics front (more on that later this year)."

If you looked at the draft/experimental[2] branch where generics development has been taking place, you can see that it has had activity as late as just last week.

In the featherweightGo presentation, Phil Wadler said Rob Pike wrote to him asking if he would be interested in working with the Go team so that they can figure out generics and try and get them right. And that is how featherweightGo came to be.

So a lot has/is been happening.

1. https://blog.golang.org/go1.15-proposals

2. https://go-review.googlesource.com/c/go/+/187317

3. https://youtu.be/Dq0WFigax_c

[pjmlp]

I stand corrected regarding the git updates.

As for the rest, it still has every chance to be shot down at last minute like it happened with the error proposal, regardless of what gets done.

[fooster]

The error proposal wasn't "shot down at the last minute". That is an entirely unfair and disinguous take on the matter.

[pjmlp]

So what is the fair way to address the community refusal and consequent introduction of a set of functions that achieve a subset of the initial proposal?

[jatone]

the error proposal was shutdown because the community rejected it due to the try function ergonomics sucking and not providing enough value.

the rest of the proposal went through just fine.

[pjmlp]

So who is to say that generics won't suffer the same fate?

[jatone]

current proposal might, but generics provide far more value than the try function from the errors proposal. they won't just stop attempting to figure it out.