Webinar
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
Cozy-cringe couture: Ugly Sweater Day
Arrow Icon
Just as wearing an “I voted” sticker has a time and a place, so too does the ugliest sweater you own. That’s right. It’s that time magical time when otherwise sensible adults deliberately dress like their grandmother's couch had a love child with a craft store explosion. The beauty of Ugly Sweater Day lies in its delicious irony – the more you fail at fashion, the more you succeed at the holiday. It's the only day of the year when "Where did you get that hideous thing?" is a genuine compliment.
Be an address ninja
Arrow Icon
We love ninjas!Yes, we do!We love ninjas!How about you? crickets We know they’re out there. BUT TODAY IS THEIR DAY, so even though these sneaky, highly-trained martial artists aren’t going to join our cheering throngs, we’ll celebrate them on National Day of the Ninja. Why?Because we’re ninja masters (sort of). We’re really good at solving every address issue just like we believe our fellow shadow warriors would—silently running in the background, solving challenges with unparalleled speed and accuracy.
EigenRisk® adds Smarty’s location intelligence resources to its global CAT risk management platform
Arrow Icon
We're happy to announce a recent partnership with EigenRisk, an insurance technology firm. Below, you will find the announcement they published on their site:ANN ARBOR, MI, December 05, 2024—EigenRisk®, a leading provider of catastrophe risk management solutions, today announced a new agreement with Smarty, a preeminent provider of address data solutions. The agreement will make Smarty’s address location intelligence and geocoding resources available through the EigenPrism® catastrophe risk management platform.