Thanks, @OladapoAjala for your interest here. This is an area which we (the Go team) should address and own because it requires potential changes in the compiler's existing tests, types2, go/types, and changes to the error handling machinery (which are currently in progress), as well as determining a model for error message formats, requiring lots of communication between stakeholders.
If you want to contribute elsewhere, please look for issues labeled with "help wanted". Generally, due to ongoing development in the type checkers, those are not good areas for larger changes at the moment (smaller bug fixes are always welcome, though).
Reminder issue.
go/types
,types2
. Fix those cases.:
vs()
) and normalize it.cc: @findleyr
The text was updated successfully, but these errors were encountered: