Robert Findley

I will fix the deadlock (I think it's my bug), but for 1.22, since presumably this has existed since 1.18.

@Nasfame thanks, I will take a look.

@Nasfame thanks for that CL, and for your investigation. I am not convinced that CL fixes the problem, because I don't think the tests are actually using the unified export...

@mdempsky thanks. I'm not sure if it's possible to do this properly with the current APIs, since SetConstraint is called from `reader.typeParamNames`, which in turn is called from the `load`...

Thanks for finding this issue. I'll look into that reproducer when I work on this (which I still plan for 1.22).

@jub0bs I think your issue may be only indirectly related, as I can only reproduce it using import/export, not with pure type checking from source (see the above CL for...

I've updated the CL above to avoid the bug by using a sync.Once to guard type param type set computation. This may be the best fix, since adding `TypeParam.Complete` is...

Looked at this briefly. We should probably not have a bug that can be reasonably triggered by an OS error, but should also do a better job of surfacing this...

First of all, I agree that the newly versioned world we live in is confusing, and I don't think we've done enough to mitigate that confusion. For example: the fact...

> The toolchain directive is ignored when using go install ...@master. Indeed, I misunderstood the `toolchain` directive as a requirement, but it is a suggestion. I'm surprised; as a suggestion...