Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/compile: regressed and non-informative error messages when return call site doesn't match return signature #48834

Open
odeke-em opened this issue Oct 7, 2021 · 1 comment
Assignees
Milestone

Comments

@odeke-em
Copy link
Member

@odeke-em odeke-em commented Oct 7, 2021

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 Applicable

What did you do?

Ran this program https://play.golang.org/p/uUOlQ-99Wx_y or inlined below

package main

func foo() (int, error) {
	return nil
}

func main() {}

What did you expect to see?

./main.go:4:2: not enough arguments to return
	have (nil)
	want (int, error)

What did you see instead?

./main.go:4:2: wrong number of return values (want 2, got 1)

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. This was one of my first contributions to the compiler driven after getting feedback from users at Gophercon 2016 fixing at least 2 issues #4215 and #6750.

Kindly cc-ing @mdempsky @griesemer

@odeke-em odeke-em added this to the Go1.18 milestone Oct 7, 2021
@odeke-em odeke-em self-assigned this Oct 7, 2021
@gopherbot
Copy link

@gopherbot gopherbot commented Oct 7, 2021

Change https://golang.org/cl/354490 mentions this issue: cmd/compile/internal/types2: report types in mismatched call arguments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants