-
Notifications
You must be signed in to change notification settings - Fork 171
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
Naming return values (?) #558
Comments
There is a very interesting discussion in the related Golang GitHub issue. |
Yep, I've read them. Actually, except the compilation optimization we can get, I also think it'll help us on code's readability. I think at this point our codebase is lack of documentation, naming return values should help that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to this article, we can get smaller and more efficient binary code generated if we name function's return values.
So I think it'll be great for Goby if we can all do this in the future and refactoring the existing code. @hachi8833 @saveriomiroddi
The text was updated successfully, but these errors were encountered: