T

Rodin 324c1936f4 docs: language source comparison — Go vs Elixir source conventions

How do the language teams build their own languages?

Key findings:
- Go: 3,428 owned TODOs (permanent, documenting limitations)
- Elixir: 127 version-gated TODOs (time-bombs with deadlines)
- Go: unsafe is 5th most-imported in its own source (1,304 times)
- Elixir: type system (13K lines) nearly as large as Kernel
- Go: 61 internal/ packages (shared-but-not-public pattern)
- Elixir: 1:1.2 test ratio vs Go's 1:3.3
- Both accept generated code, different delivery (checked-in vs compile-time)

2026-04-30 12:19:32 -07:00

analysis

docs: language source comparison — Go vs Elixir source conventions

2026-04-30 12:19:32 -07:00

elixir

docs: Elixir patterns vs official guidelines with code examples + hypotheses

2026-04-30 07:58:31 -07:00

docs: enhance Go divergence analysis with code examples + hypotheses

2026-04-30 07:57:37 -07:00

README.md

docs: Go patterns vs official guidelines divergence analysis

2026-04-30 07:50:32 -07:00

README.md

Patterns vs Official Guidelines

Divergence analyses comparing our extracted-from-source patterns against official coding guidelines.

Reports

Ecosystem	Our Patterns	Official Guidelines	Report
Go	rodin/go-patterns	Effective Go, Code Review Comments, Google Style	go/
Elixir	rodin/elixir-patterns	CONTRIBUTING.md, Style Guide, HexDocs	elixir/

Philosophy

Official guides tell you what to do. Source patterns show what mature code actually does. When they diverge, neither is wrong — they serve different audiences and optimize for different things.

This repo documents where they agree, where they differ, and why.