Rodin
725308c37a
Not just per-file patterns — structural analysis of how these codebases organize at scale. Key findings: - 116 packages @ 4 files each (CockroachDB) - Interface layer breaks circular deps - Testability designed in, not bolted on - Composition via data, not inheritance
Go Patterns
Idiomatic Go patterns extracted from the Go standard library source code with verified file:line citations.
Structure
patterns/— Go stdlib patterns (interfaces, errors, concurrency, structs, testing, docs, style, API conventions, packages)smells/— Anti-patterns and common Go mistakeschangelog/— Daily digest of merged Go PRs
Philosophy
These rules are derived from what the Go standard library actually does, not opinions or blog posts. Every pattern cites specific files and line numbers.
When unsure how to do something in Go, look at how the standard library does it.