1 Commits
Author SHA1 Message Date
clawbot d22642c2b5 CODE_STYLEGUIDE_GO: propose naming rules (closes #174)
check / check (push) Successful in 1m24s
Adds a Naming section to the Go style guide: eight rules for package
names, ten for exported names as the caller reads them, and two for
local names. Each is one rule with its reason.

The sentence that banned `util` now points to the section, which bans
it along with `model`, `common`, `types`, `helpers`, `api` and the
like, and says what to name the package instead.

This is a proposal. Nothing is renamed in any repo until sneak
approves or amends the rules.

Model: fable-5-2
2026-11-16 05:21:35 +00:00
+33 -48
View File
@@ -221,7 +221,7 @@ last_modified: 2026-11-16
...
if err != nil {
SendErrorResponse(w, ErrBadRequest)
SendErrorResponse(w, MSGenericError)
return
}
@@ -501,27 +501,19 @@ exported name, and reads them as one name: `http.Server`, `list.New`.
run together (`tabwriter`, never `tab_writer` or `tabWriter`), because that
is how the standard library spells every package name.
1. Never use a package name from the list below, or anything else that says
nothing about what is in it, because every program has a data model, helpers
and types.
- `model` and `models`
- `util` and `utils`
- `common`
- `misc`
- `helper` and `helpers`
- `types`
- `interfaces`
- `api`
1. Split a package whose code is about several things, so that each part can be
named for what it provides (`stringset`, not `util`).
1. Never name a package `model`, `models`, `util`, `utils`, `common`, `misc`,
`helper`, `helpers`, `types`, `interfaces` or `api`, or anything else that
says nothing about what is in it: every program has a data model, helpers
and types. Name the package for the one thing its code is about; when its
code is about several things, split it first (`stringset`, not `util`).
1. Spell a word out unless its short form is the one everybody already uses
(`fmt`, `strconv`), because any other abbreviation has to be decoded.
1. Never give a package a name that callers want for a variable (`buf`) or that
a widely used standard package has (`log`), because importers must rename
one of the two.
1. Never give a package a name that callers want for a variable (`buf`,
`count`) or that a widely used standard package has (`log`, `http`, `url`),
because every importer then has to rename one of the two. Use a longer name
that says which one: `bufio`, `usercount`.
1. Give a package's directory the package's name, package `main` excepted, so
that the import path ends in the name the code uses.
@@ -530,51 +522,44 @@ exported name, and reads them as one name: `http.Server`, `list.New`.
plus `test` (`storetest`, never `testutil` or `testhelper`), because the
name then says whose tests it is for.
1. Import a package under its own name unless two imports share a name or its
own name breaks these rules, so that a reader knows it without checking the
imports.
1. Give a renamed import the same local name in every file, so that one name
always means one package.
1. Import a package under its own name. Give it a local name only when two
imports have the same name or its own name breaks these rules, and use that
local name in every file, so that one name always means one package.
## Exported names
1. Never repeat the package name inside a longer exported name (`http.Server`,
not `http.HTTPServer`; `yamlconfig.Parse`, not
`yamlconfig.ParseYAMLConfig`), because the caller has already written it.
The type a package is named for may carry the same name on its own:
`list.List`, `time.Time`.
1. Use the same plain name in two packages when it fits both (`bufio.Reader`,
`csv.Reader`), because the package name already tells them apart.
1. Leave the receiver's type out of a method name, and the parameter and result
types out of a function name (`(c *Config) WriteTo(w)`, not
`WriteConfigTo`), because the signature already states them.
`WriteConfigTo`), because the signature already states them. Only when two
functions differ in nothing but a type does the type go in, at the end:
`ParseInt`, `ParseInt64`.
1. Put a type at the end of a function's name when the type is the only
difference between two functions (`ParseInt`, `ParseInt64`), because Go
needs a different name for each.
1. Use a noun for a function that returns something and a verb for one that
does something (`JobName(key)`, `WriteDetail(w)`), so that a call reads as
what it gives or does.
1. Name a function that returns a value for the value and one that acts for the
action (`JobName(key)`, `WriteDetail(w)`), so that a call reads as what it
gives or what it does.
1. Never start a getter with `Get` (`Owner()`, not `GetOwner()`; the setter is
`SetOwner()`), because the capital letter already tells the method from the
field.
1. Begin the name of a database or network call with a verb that says so
(`Fetch`, `Load`), because the reader must know it can be slow or fail.
field. A call that goes to a database or the network takes a verb that says
so (`Fetch`, `Load`), and `Get` stays only where it is the thing's own word,
as in an HTTP GET.
1. Name a one-method interface for its method plus `er` (`Reader`,
`Formatter`), because the name then says the one thing a value of it does.
1. Use a well-known method's name and signature for a method that does the same
thing (`String()`, never `ToString()`), because readers and the standard
interfaces expect them.
1. Never reuse a well-known method name (`Read`, `Write`, `Close`, `String`)
for a method with another meaning or signature, because readers rely on each
name meaning one thing.
1. Give a method that does what a well-known method does that method's name and
signature: `String()`, never `ToString()`. Give a method that does anything
else another name, because readers and the standard interfaces rely on
`Read`, `Write`, `Close` and `String` meaning one thing.
1. Write an initialism in one case throughout (`ServeHTTP`, `appID`, `URL` or
`url`; never `Url`, `Id` or `Http`), because that is how the standard
@@ -590,13 +575,13 @@ exported name, and reads them as one name: `http.Server`, `list.New`.
## Local names
1. Match a local name's length to how far from its declaration it is used (`i`
in a short loop), because a reader far from the declaration has only the
name.
1. Match a local name's length to the distance between its declaration and its
last use (`i`, `r` and `db` across a few lines, a full word or two across a
long function), because a reader far from the declaration has only the name.
1. Name a receiver with one or two letters, the same in every method of its
type, never `this`, `self` or `me`, because its role is plain from the
method.
type, never `this`, `self` or `me`, because it appears on nearly every line
of those methods.
# Other Golang Tips and Best Practices (Optional)