rust-lang/rust Adopts an LLM Policy: 'Fine to Analyze, Distill, Check, Review — Not to Create'

Inside Rust Blog·medium signalXBlueskyLinkedInCopy link

Five Rust teams reached consensus on a policy (authored by Jynn Nelson, published August 5) scoped to the rust-lang/rust monorepo. Allowed: answering questions, analysis, distillation, refinement, checking, suggesting, reviewing; machine translation and LLM-found bugs require disclosure. Restricted: creating code changes unless pre-arranged, non-critical, high-quality, well-tested and disclosed; generating public docs; unmarked LLM-written PR descriptions or comments; soundness-critical changes are strongly discouraged even for domain experts. The stated reasoning is worth reading for anyone maintaining an OSS project — polished PRs no longer signal effort or understanding, generation worsens an existing review-bandwidth problem, and LLM-to-LLM copy-paste in review threads wastes maintainer time.