Go Style: Difference between revisions
Jump to navigation
Jump to search
(→Naming) |
|||
| Line 11: | Line 11: | ||
=<span id='Identifiers'></span>Naming= | =<span id='Identifiers'></span>Naming= | ||
{{External|https://google.github.io/styleguide/go/guide#mixedcaps}} | {{External|https://google.github.io/styleguide/go/guide#mixedcaps}} | ||
Naming is one of the most important aspects of Go development. Writing idiomatic Go requires understanding of its core naming principles. | |||
[[Go_Language#Identifiers_.28Names.29|Identifiers]] should use camel case: <code>SomeColor</code> or <code>someColor</code>. Do not use snake case (<code>some_color</code>). | [[Go_Language#Identifiers_.28Names.29|Identifiers]] should use camel case: <code>SomeColor</code> or <code>someColor</code>. Do not use snake case (<code>some_color</code>). | ||
Revision as of 02:17, 6 September 2023
External
- https://google.github.io/styleguide/go/
- https://go.dev/doc/effective_go
- https://github.com/golang/go/wiki/CodeReviewComments
Internal
Overview
The Go standard library is a good source of code examples, comments and style.
Naming
Naming is one of the most important aspects of Go development. Writing idiomatic Go requires understanding of its core naming principles.
Identifiers should use camel case: SomeColor or someColor. Do not use snake case (some_color).