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

all: move to Camel Case naming #37

Open
donkahlero opened this issue Jul 2, 2018 · 0 comments
Open

all: move to Camel Case naming #37

donkahlero opened this issue Jul 2, 2018 · 0 comments

Comments

@donkahlero
Copy link
Collaborator

As discussed e.g. in #35, we should move to the Go-way of using Camel Case, as described in Effective Go.

Right now, we are dealing with a mixture of both Camel Case and more C_style variable names.
donkahlero added a commit that referenced this issue Jul 8, 2018
@donkahlero
all: moves to camel case naming
2d45916 
This patch is in regard to issue #37
and features a major renaming of all affected variables.
@donkahlero donkahlero mentioned this issue Jul 8, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@donkahlero