Thanks for bringing this up. It's a fair point.
Note though that it won't be possible to instantiate foo because there's
no type argument that would implement C; so it's not possible to get to an
incorrectly running program here.
We also don't report an error when a type set is empty.
But you ar
Thanks for raising this issue. This is clearly a bug in the spec, or at the
very least "an imprecision". Hopefully this is
better: https://go-review.googlesource.com/c/go/+/375799 .
The set of specific types is an approximation for the actual type set. In
practice we only need to consider those
Correction: The last paragraph in the post below should have said: "In Go,
type information is not available at *parse* time". (Of course, type
information is available at compile time.)
On Tuesday, July 14, 2020 at 2:56:01 PM UTC-7 gri wrote:
> We have received a variety of feedback on the gen
