Go Guidelines

Overview

Idiomatic Go guidelines based on Effective Go and Google Go Style Guide. Go has its own conventions — writing good Go means embracing them, not porting patterns from other languages.

Core Proverbs

• Clear is better than clever — optimize for readability, not cleverness
• A little copying is better than a little dependency — duplicate small functions rather than import heavy packages
• The zero value should be useful — design types so var x T works without initialization
• Don't communicate by sharing memory; share memory by communicating — use channels
• Errors are values — program with them, don't just check them
• Don't just check errors, handle them gracefully — add context, decide action
• Reflection is never clear — avoid reflect unless building frameworks

Formatting