On Sat, Mar 4, 2023 at 5:49 PM Lenny 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
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
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
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
Keith, thank you very much for your feedback, it is highly appreciated!
With this in mind, it's time for lies, more lies, and statistics,
benchmarking the three different implementations below:
func (r *Reader) Uint32() uint32 {
if r.err != nil {
return 0
}
var s struct {
_ [0]uint32
b [4]byte
