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?

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.

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

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.

> 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.

It doesn't matter how hard anybody tries when a vocal community rejects any attempt at changing Go type system.