all: move to Camel Case naming
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 135
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
As discussed e.g. in https://github.com/gonum/hdf5/pull/35, we should move to the Go-way of using Camel Case, as described in [Effective Go](https://golang.org/doc/effective_go.html#mixed-caps).
Right now, we are dealing with a mixture of both Camel Case and more C_style variable names.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the naming discussion in pull request #35 and the linked Effective Go MixedCaps guidance. Inventory the C_style and Camel Case names across the project, then define the full conversion scope and verify that naming is consistent without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100