[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Naming return values (?) #558

Open
st0012 opened this issue Jan 1, 2018 · 2 comments
Open

Naming return values (?) #558

st0012 opened this issue Jan 1, 2018 · 2 comments
Assignees
@st0012
Labels
Needs feedback Priority Medium question Refactoring
Milestone
version 0.2.0

Comments

@st0012
Copy link
Member
st0012 commented Jan 1, 2018

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
@st0012 st0012 added this to the version 0.1.7 milestone Jan 1, 2018
@st0012 st0012 self-assigned this Jan 1, 2018
@64kramsystem
Copy link
Member
64kramsystem commented Jan 2, 2018 •
edited
Loading

There is a very interesting discussion in the related Golang GitHub issue.

@st0012
Copy link
Member Author
st0012 commented Jan 2, 2018

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.
And I know there's a potential risk about shadowing variables, but I think it can be avoid if we use proper IDE or editors.

@st0012 st0012 modified the milestones: version 0.1.7, version 0.2.0 Jan 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@st0012 st0012

Labels
Needs feedback Priority Medium question Refactoring
Projects
None yet
Milestone
version 0.2.0
Development

No branches or pull requests
2 participants
@64kramsystem @st0012