Nevkontakte

That does sound like a bug. I think there are a fair few issues around edge cases of struct embedding handling and this looks like one of them.

I like this idea, I think it would help avoiding a lot of possible pitfalls (aka know bugs :) ). I would also propose to integrate it into the gopherjs...

I think because it would also be a standalone tool, it makes most sense to keep it in a separate repository, but I could be convinced otherwise.

Might be worth asking in the gopher slack #tools channel, but I feel like option #1 is the only one really viable. It is really unfortunate that multichecker doesn't optionally...

I agree with the general sentiment. I think the only feature github actions doesn't support (and why I didn't actively attempt to move off circleci so far) is automated test...

Yes, I think your hypothesis is correct.

I suspect this isn't so much as our bug as `go/build` one. This would be a great deal easier to fix after https://github.com/gopherjs/gopherjs/issues/1021, especially if we switch to go/packages instead...

So [here](https://github.com/gopherjs/gopherjs/blob/1cd471b6ad88ceb485b015337b360bf8a79a7acb/build/build.go#L61-L64) we fall back to the embedded VFS if the primary build context doesn't find a package. This was done to avoid weirdness when a projects go.mod specifies a...

Hi @chenrui333, I am acutely aware of this :) Unfortunately, I have only limited amount of time for open source work, and all of it is currently going towards adding...

I agree with @flimzy, although I feel like supporting 1.18 would seem redundant after 1.19-beta release. In the other news, my alternate generics branch is _very_ close to fully supporting...