Golang go/types: mismatching 'indirect' results from NewMethodSet and LookupFieldOrMethod for interface methods

For T below, we get different results for whether or not m is indirect when using the NewMethodSet vs LookupFieldOrMethod APIs:

type T interface{ m() }

https://go.dev/play/p/yvswbEovSem

Unless I'm misunderstanding, these APIs should agree.

CC @griesemer

Comment From: ianlancetaylor

@findleyr @griesemer What is the current status here? This issue is currently in the 1.19 milestone. Should it move to 1.20? To Backlog? Thanks.

Comment From: findleyr

This bug has existed for a long time. Let's try to fix for 1.20.

Comment From: findleyr

Unfortunately we don't have bandwidth for this fix, and it is a low priority. Moving to 1.21.