Mark
Mark
Just to note, the commit for that recent failure is before the fix.
I've done a bit of poking — somewhat interesting to me is that the below panics: ``` type AB = A[B] type _ struct { _ AB } type B...
I suspect the below (from `typInternal`) is related: ``` case *syntax.Operation: if e.Op == syntax.Mul && e.Y == nil { typ := new(Pointer) typ.base = Typ[Invalid] // avoid nil base...
@findleyr Oftentimes, when we assign a type to `Invalid`, we emit an error then and there and continue type checking. However, that does not _always_ happen. In particular, aliases use...
It seems that doing this via the `Alias` type is appropriate. I checked `go/types` and the issue replicates there as expected. Interestingly, with `gotypesalias=0`, the check added in [CL 379916](https://go.dev/cl/379916)...
After some slight adjustment to handle the case of partial type checking, things seem to be in order. I'm going to consider this all but submitted.