Why the Rust Core Team Is Begging Developers to Stop Submitting AI‑Generated Garbage PRs

In a time when large‑model hype dominates social media, Tony Bai introduces an internal Rust discussion initiated by language designer Niko Matsakis, who spent weeks gathering honest opinions from Rust core contributors about AI‑assisted programming.

When AI Becomes a Catalyst for Blind Confidence

Many view AI as a mentor for beginners, but Rust maintainers see the opposite: AI acts as a catalyst for developers’ overconfidence. One contributor bluntly states:

"AI gives developers who are ashamed of submitting low‑quality code a false ‘official approval’ stamp. For those suffering from the Dunning‑Kruger effect, AI acts as a catalyst, inflating their confidence while severely eroding their actual ability."

Traditionally, submitting a PR requires deep understanding of the codebase, design philosophy, and countless contextual variations—a natural filter. Now, a developer can simply feed an error message to a model like Claude Code, receive seemingly perfect Rust code, and blindly run git commit without grasping lifetimes or ownership.

Maintainers Tormented by the AI “Megaphone”

The real pain point is contributors acting as a “megaphone” between reviewers and the model. As one maintainer complained:

"Some contributors even act as a ‘megaphone’ between reviewers and the large model! They copy my review comments, feed them to the model, and paste the model’s gibberish back to me. Please, for the love of God, stop! This drives me to extreme burnout."

Such behavior not only wastes time but also tramples the open‑source community’s trust contract.

Two Extreme Responses

Extreme One: Moral Purity and Total Ban

Some veterans argue that all LLMs are built on stolen data and consume massive energy, urging a complete ban on AI‑generated PRs and demanding proof that code is written entirely by humans.

Extreme Two: Use Magic to Defeat Magic

Recognizing the inevitability of AI, Matsakis and others propose defensive architectures that leverage AI itself to filter harmful contributions. Their recommendations include:

Introduce “spam‑filter”‑level review thresholds, such as a “Web‑of‑Trust” system where only contributors with proven high‑quality history receive priority review.

Require a mandatory “anti‑AI disclaimer” where authors affirm full understanding of every line and pledge not to copy model output verbatim.

Deploy an AI gatekeeper that automatically scans incoming PRs for “seemingly reasonable but actually absurd” logic flaws before human reviewers see them.

The Zero‑Pay Exploitation

AI giants like OpenAI and Anthropic, valued at hundreds of billions, profit from Rust code while the unpaid maintainers who clean up the resulting garbage receive no compensation. One core member suggested:

"Perhaps we should approach those AI companies (which also heavily use Rust internally) and ask them to fund our maintainers. Even though many morally oppose these firms, I still hope to take their money to support our brothers."

This mirrors a scenario where a massive delivery platform dumps endless orders at a community’s doorstep, leaving unpaid volunteers to clean up.

Conclusion

The memo serves as a stark warning to developers dazzled by AI’s promises. While many acknowledge AI’s empowerment—automating tedious scripts and documentation—its power cannot mask the mediocrity of its users. Only when a developer truly masters ownership, the borrow checker, and low‑level memory layout, can AI‑generated code be responsibly integrated; otherwise, they remain cheap code movers for AI corporations.

Maintainers are urged to stay vigilant, preserve trust, and focus on system‑level design thinking and engineering philosophy that AI cannot replace.