As far as I can tell there are already a lot of closed working as intended tickets related to
https://go.googlesource.com/proposal/+/refs/heads/master/design/go2draft-type-parameters.md#using-generic-types-as-unnamed-function-parameter-types My suggestion is to be more proactive about this specific problem as soon as consensus is reached by introducing a `go vet -generic` flag that does nothing more then just highlight this specific very rare problem. And introduce this small language change now so it's more than a year in advance in place. The concern I think will come forward is when we don't give it a high enough priority early enough it will significantly handicap the generic error compiler messages if we don't be concrete about it? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f396c1dc-1766-452f-8fc8-aaa09c42ba6cn%40googlegroups.com.
