New 42-day free trial
Smarty

Go naming conventions

Smarty header pin graphic
Michael Whatcott
Michael Whatcott
 • 
October 18, 2018
Tags

It's been said that naming is one of the two hardest problems in computer science, along with cache invalidation and 'off-by-one' errors. (See what I did there?) Do you ever find yourself wondering what policies and practices you could adopt to make your life easier when reading code you wrote months ago? Or maybe you're up at night wishing you knew how to write code in such a way as to maximize adoption and convenience for your users? Well, look no further because we've anticipated the need, solved the problem, and now we're sharing our knowledge and wisdom at no charge, all out of the goodness of our hearts in this comprehensive, totally no-nonsense (nudge, nudge, wink, wink) style guide of Go naming conventions.

What you’re about to read might actually be helpful at some point, but we're not betting on it. Don't try this at home...actually, do try this at home--but maybe don't try it at work.

Table of contents

  1. Export local variable names
  2. Export local const names
  3. Export input argument names
  4. Export output arguments names
  5. Export reciever names
  6. Use single-character receiver names
  7. Use single-letter argument names
  8. Use double-letter names when you run out of single-letter
  9. Actually, use a generic receiver name like 'this',
  10. For added emphasis, use extended unicode characters for receiver names
  11. Always define import aliases
  12. Always export all imports
  13. Use single-letter (exported) import aliases
  14. In the spirit of #8 (above), use double-letter alias names when necessary

1: Export local variable names

package main

import "fmt"

func main() { Message := "Always export local variable names" fmt.Println(Message) }

https://go.dev/play/p/8WVCvJpoa59

2: Export local const names

package main

import "fmt"

func main() { const Message = "Always export constants defined in functions" fmt.Println(Message) }

https://go.dev/play/p/-0yZhHVNOOs

3: Export input argument names

package main

import "fmt"

func main() { Print("Always export input argument names") }

func Print(Message string) { fmt.Println(Message) }

https://go.dev/play/p/utRBMOMQNgj

4: Export output arguments names

package main

import "fmt"

func main() { Print("Always export output argument names") }

func Print(Message string) (N int, Err error) { return fmt.Println(Message) }

https://go.dev/play/p/n5cJhLDKNWk

5: Export reciever names

package main

import "fmt"

func main() { new(Printer).Print("Always export receiver names") }

type Printer struct{}

func (Printer *Printer) Print(Message string) (N int, Err error) { return fmt.Println(Message) }

https://go.dev/play/p/jEN-zkrjxdT

6: Use single-character receiver names

package main

import "fmt"

func main() { new(Printer).Print( "Use only the first letter of a type as the receiver for its methods (oh, wait...), " + "and (per tip #5) make sure the receiver is exported") }

type Printer struct{}

func (P *Printer) Print(Message string) (N int, Err error) { return fmt.Println(Message) }

https://go.dev/play/p/0OqQLnPPcVd

7: Use single-letter argument names

package main

import "fmt"

func main() { new(Printer).Print("Use single-letter variables whenever possible") }

type Printer struct{}

func (P *Printer) Print(M string) (N int, E error) { return fmt.Println(M) }

https://go.dev/play/p/Q1jgH_6h2kT

8: Use double-letter names when you run out of single-letter names

package main

import "fmt"

func main() { new(Printer).Print("Use double-letter variables when you run out of single-letter variables") }

type Printer struct{}

func (P *Printer) Print(NN string) (N int, E error) { return fmt.Println(NN) }

https://go.dev/play/p/k3p9Hf49-20

9: Actually, use a generic receiver name like 'this', 'self', or 'me'

package main

import "fmt"

func main() { new(Printer).Print("On second thought, use a generic receiver name like 'this', 'self', or 'me'.") }

type Printer struct{}

func (this *Printer) Print(NN string) (N int, E error) { return fmt.Println(NN) }

https://go.dev/play/p/mSMZRqUy4qw

10: For added emphasis, use extended unicode characters for receiver names

package main

import "fmt"

func main() { new(Printer).Print("See what I did here? ;)") }

type Printer struct{}

func (𝕥𝕙𝕚𝕤 *Printer) Print(NN string) (N int, E error) { return fmt.Println(NN) }

https://go.dev/play/p/VPpSDOZYYjT

11: Always define import aliases

package main

import fmt "fmt"

func main() { fmt.Println("Always define import aliases") }

https://go.dev/play/p/zCOnEoNtAf4

12: Always export all imports

package main

import Fmt "fmt"

func main() { Fmt.Println("Always export all imports") }

https://go.dev/play/p/_fEPiypASub

13: Use single-letter (exported) import aliases

package main

import F "fmt"

func main() { F.Println("Use single-letter (exported) import aliases") }

https://go.dev/play/p/e8JQAlSKpnZ

14: In the spirit of #8 (above), use double-letter alias names when necessary

package main

import ( F "flag" FF "fmt" )

func main() { F.Parse() FF.Println("Use double-letter alias names when necessary") }

https://go.dev/play/p/U0ac86PHUsb

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?