Never use a pointer to an interface type. Pass interfaces as values, since an interface already provides reference semantics to the underlying data.
Interfaces are reference types; taking a pointer to an interface is unnecessary and can lead to confusion. It complicates function signatures without any benefit, and it doesn't change the fact that the underlying data can be a pointer.
Side-by-side examples engineers can pattern-match during review.
type Fooer interface { Foo() }
func UseFoo(f *Fooer) {
// ... using pointer to interface (unnecessary)
}type Fooer interface { Foo() }
func UseFoo(f Fooer) {
// ... using interface directly
}type Fooer interface { Foo() }
func UseFoo(f *Fooer) {
// ... using pointer to interface (unnecessary)
}type Fooer interface { Foo() }
func UseFoo(f Fooer) {
// ... using interface directly
}From the same buckets as this rule.
All static JS/CSS/font/image files MUST use content-hashed filenames (e.g., app.9c1a7b.js) and be served with "Cache-Control: public, max-age=31536000, immutable". HTML and other non-fingerprinted documents MUST be served with "Cache-Control: no-cache" (or equivalent) to enable conditional revalidation.