Naming conventions in go?

[Lenny]

The effective go documentation doesn't really go into detail of whether or not I should try to name my variables as short as possible even though that is discouraged because of readability

[peterGo]

Lenny,'

Go Code Review Comments
Variable Names
https://github.com/golang/go/wiki/CodeReviewComments#variable-names

Google Style Guides
Go Style
Variable names
https://google.github.io/styleguide/go/decisions#variable-names

What's in a name?
https://talks.golang.org/2014/names.slide

Names
https://research.swtch.com/names

Notes on Programming in C
http://doc.cat-v.org/bell_labs/pikestyle
Variable names

peter

[Kurtis Rader]

On Sat, Mar 4, 2023 at 5:49 PM Lenny <develope...@gmail.com> wrote:

The effective go documentation doesn't really go into detail of whether or not I should try to name my variables as short as possible even though that is discouraged because of readability 

Lookup "bike shedding". Whether a very short variable name (e.g., "i") or very long name (e.g., "CurrentIndex") is appropriate depends on context. And that context is not just a particular language feature (e.g., a "range" loop in Go) but also the idioms employed by a particular project. Whether a particular name maximizes readability depends on the context -- not the number of characters in the name.

--

Kurtis Rader

Caretaker of the exceptional canines Junior and Hank