go/types, types2: consolidate error message formats #49123
Labels
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
Error messages don't have a particular "style guide" at the moment:
func main must have no arguments and no return values
:
:undefined: x
;
:cannot make int; type must be slice, map, or channel
cannot slice s (variable of type chan int)
Maybe we can come up with a reasonably consistent set of rules for how to format errors (e.g., when to use ':', ';', or parentheses). If we can, that we should be able to encode this for consistent behavior.
The text was updated successfully, but these errors were encountered: