New 42-day free trial Get it now
Smarty

Go naming conventions

Smarty header pin graphic
Updated October 29, 2025
Tags
Smarty header pin graphic

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.
Read our recent posts
USPS API rate limit capped at 60 requests per hour: How to prepare and why many are choosing Smarty
Arrow Icon
Because who doesn’t love juggling one more thing during the holiday season…? A major shift in the address-verification landscape is approaching at the beginning of the new year. On January 25, 2026, the United States Postal Service (USPS) will officially retire its long-standing Web Tools APIs, a free API that previously allowed for approximately 5 address lookups per transaction. This includes the legacy USPS Address Information APIs that many organizations have depended on for years. Under USPS’s new API structure, the default quota for many services, including the Addresses API, is 60 requests per hour.
Pinpoint 2025: Day 1 recap
Arrow Icon
For two days, Smarty users gathered together with other address data experts for Pinpoint, Smarty’s first virtual user conference, where developers, industry experts, and product specialists talked all things addresses and pulled back the curtain on address data solutions. Attendees asked questions about cloud-based software, the impact of accurate address data on fintech and insurance companies, and the ROI of good address data across all industries. Plus, attendees got to take a peek behind the scenes and see what makes Smarty’s address data solutions tick.
Pinpoint 2025: Day 2 recap
Arrow Icon
For two days, Smarty gathered address data experts for Pinpoint, our first-ever virtual user conference. There, developers, product specialists, and industry experts delved into the nitty-gritty details of address data that you need to understand in order to succeed in your industry. Attendees learned how to process addresses faster (much faster) than the blink of an eye, with and without using code! They also got to look under the hood on how insurance is evolving and becoming even more efficient than ever to create a “delightful user experience.

Ready to get started?