A compact, practical guide for writing production-quality Go. The document codifies rules and examples around pooled resource lifetimes, safe concurrency patterns, numeric size handling, robust error handling, and disciplined testing practices. It focuses on avoiding common pitfalls that cause races, memory issues, and flaky tests.
Refer to these guidelines during code review, when authoring concurrent or pooled-resource code, before changing APIs that affect ownership semantics, and when writing tests that depend on GC or allocation expectations. Also useful as an input to automated repair/workflow coders that enforce project conventions.
Developer assistance agents, review automation, and workflow coders that embed project-specific fix prompts (e.g., workflow-coder).
Cette compétence n'a pas encore été examinée par notre pipeline d'audit automatisé.
