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
Falling out of love with your address data solution?
Arrow Icon
There are plenty of address data solutions in the sea. You might need to let them off the hook if:Their data accuracy is sufferingToo many false positivesSpotty data availability (lack of international support? Beuller?)Off-the-mark geocoding (not truly rooftop-level accurate)Missing data enrichment (RDI, FIPS, unique ID, secondary addresses, etc. )They don’t flirt nicely (or at all) with your existing systemsThey don’t have an accurate address autocomplete solutionYour relationship with them has become robotic and mundane (When you need help, you have to talk to a robot instead of a real person for support… ew.
Global game-changer: Level up your customer retention in 2025
Arrow Icon
In 2024, it’s estimated that online purchases, or ecommerce, made up more than 20% of global retail, with 2. 77 billion people shopping online, and those numbers will only get bigger in the following years. With so much online shopping, more goods and services are being shipped than ever before—including during the height of the Sears catalog in 1970. Side note: If you’re reading this and you don’t know what the Sears catalog was or how much it impacted the average home, it’s worth taking a trip down memory lane and seeing how your elders used to shop.
Shipping optimization: Boosting your bottom line
Arrow Icon
Shipping optimization is rapidly evolving the retail landscape with advancements in shipping technology. From using robotics to increase efficiency and protect workers from dangerous jobs to autonomous vehicles and drones taking items to hard-to-reach areas, shipping has drastically evolved from the infancy of ecommerce in the 1990s. Sure, the 90s are currently having a pop culture resurgence, but your customers don’t want their shipping experience to go retro. One of the most impactful ways to ship effectively is to use a Shipping Execution System (SES).

Ready to get started?