We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Relates to issue #28160
Go1 spec allows for 2 different return statement styles causing unnecessary added complexity and confusion for some developers.
Using an example func from the spec:
func complexF3() (re float64, im float64) { re = 7.0 im = 4.0 return } // vs func complexF3() (re float64, im float64) { re = 7.0 im = 4.0 return re, im }
This proposal is to remove implicitly returned result parameters from the spec, thereby requiring result parameters to always be explicitly returned.
The text was updated successfully, but these errors were encountered:
Duplicate of #21291 ?
Sorry, something went wrong.
Yes it is, thank you @deanveloper
@kf6nux please continue the discussion there.
Sorry, I did search ahead of time and missed it. Thanks for the link!
No branches or pull requests
Relates to issue #28160
Go1 spec allows for 2 different return statement styles causing unnecessary added complexity and confusion for some developers.
Using an example func from the spec:
This proposal is to remove implicitly returned result parameters from the spec, thereby requiring result parameters to always be explicitly returned.
The text was updated successfully, but these errors were encountered: