Here another example, probably related: https://gotipplay.golang.org/p/FBFHzcZOTmX

package main

func main() {
	X(Interface[*F[string]](Impl{}))
}

func X[Q Qer](fs Interface[Q]) {
}

type Impl struct{}

func (Impl) M() {}

type Interface[Q Qer] interface {
	M()
}

type Qer interface {
	Q()
}

type F[A, B any] struct{}

func (f *F[A, B]) Q() {}

This produces the errors:

./prog.go:4:3: *F[string] does not satisfy Qer (missing method Q)
./prog.go:4:14: *F[string] does not satisfy Qer (missing method Q)
./prog.go:4:15: cannot infer B (prog.go:22:11)
./prog.go:4:15: got 1 arguments but 2 type parameters

The type F does have a method Q so the first two error messages are misleading.
Also, those messages come before the actual cause of the error (that we're only passing
one type parameter when we should be passing two), which adds to the confusion.

/cc @griesemer

The underlying issue here is that some of the checks must be done in a delayed fashion, leading to some confusing scenarios like this one.

This is just a bug.

cc: @findleyr

Change https://golang.org/cl/378175 mentions this issue: go/types, types2: avoid field/method lookup error on invalid types