Cody Oss

Closing due to lack of response.

I am not sure there is a good solution for this. If you read the comment above that block of code this is done for a reason. Thoughts?

I will leave this issue open for discussion. I am not sure this is something we should be adding to the API though. The EXPECT API is explicit on purpose....

This seems like a reasonable change, but it is breaking so holding off for now.

Hey, I am not against not using `go list` but using it fixed a couple bugs for use. The advantages we gained by it were: 1. It is module aware....

Thanks for opening this issue, I agree this is something that should be addressed. I would like to leave this issue open a bit to collect user experiences. I know...

One difference is how type aliases are handled, works correct in source mode: https://github.com/golang/mock/issues/244

mocking unexported interfaces requires source mode: #297

@n0trace Thanks for the PR! Would you be willing to expand support for this test case as well: ``` type EmbeddingIface interface { TwentyOne[other.Three] other.Twenty[StructType] Foo() error } ``` If...

@n0trace Sorry if I was not clear, I meant just copy paste that code literally into generics.go. I don't think this solution covers the case where the outer interface does...