cmd/compile: regressed and non-informative error messages when wrong arguments/counts are passed into a function call #48835
Labels
FrozenDueToAge
okay-after-beta1
Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1
release-blocker
Milestone
What version of Go are you using (
go version
)?GoTip at 6f74ed0 aka Go1.18
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)? Not ApplicableWhat did you do?
Ran this program https://play.golang.org/p/Md3pUBvDKk8 or inlined below
What did you expect to see?
What did you see instead?
This is a regression from Go1.8 and it is unique in the upcoming Go1.18; I understand there have been compiler rewrites but just a count of arguments takes us back to square 0 where we were, yet we had worked on improving the user experience of these messages. I had gotten feedback from users at Gophercon 2016 about how the change that we implemented would improve life for them.
Kindly cc-ing @mdempsky @griesemer
The text was updated successfully, but these errors were encountered: