Login
You're viewing the techdon.dev public feed.
  • Aug 11, 2026, 11:23 AM

    I just read the @rust 's LLM policy. Not only is it stupid as hell, it's **extremely** confusing.

    "You must not use LLM to create"
    "You must not force others to read LLM-generated content"

    but then

    "You must disclose the use of LLM"

    What exactly am I disclosing and why? What the actual fuck??

    The exact wording is:

    "Pre-arranged, non-critical, high-quality, well-tested, and well-reviewed code changes that are originally created by an LLM are allowed, with disclosure."

    What exactly does that mean? How am I supposed to get my changes "well-reviewed" if I can't put them in a PR first?

    And whoever wrote this blog post, obvious doesn't know that LLMs can also be used to detect and/or filter pure vibe-coded low-quality/shitty PRs.

    💬 1🔄 0⭐ 2

Replies

  • Aug 11, 2026, 11:53 AM

    @zeenix @rust They could've had this policy much less confusing and shorter by just saying that LLM contributions are forbidden. That's effectively the same thing as what they're writing now in too many words.

    💬 2🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Aug 11, 2026, 12:23 PM

    @slomo @zeenix Here's an example where you're allowed to use an LLM:

    ℹ️ Changes are trivial if there is no other way to write them, or the other ways to write them are nearly identical. For example, the following are all trivial:
    - Typo fixes
    - Markdown links
    - Changing a word to a synonym
    - Type signatures for a trait implementation

    So, LLM allowed, but only with disclosure

    💬 0🔄 0⭐ 0
  • Aug 11, 2026, 12:39 PM

    @diondokter @zeenix Yes, I read the actual policy too. That's equivalent to basically not allowed :)

    It's pretending that there is some kind of compromise but that's actually not the case. Nobody* is going to use LLMs for such trivial changes and if they did the result would be indistinguishable from using other, more simple tooling (e.g. a spell checker, or sed) so there's not even any point in disclosing the use of an LLM.

    That's perfectly fine FWIW. Their choice. But it would be nice to be clearer about that.

    * Nobody might be a bit strong. I saw PRs of people fixing typos with Claude Fable. But that's probably more a sign of someone being confused than normal practice.

    💬 2🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Aug 11, 2026, 12:43 PM

    @slomo @zeenix It also leaves room for (private) LLM review. Maybe it spotted an off-by-one error and inserted the `+ 1` for you. You don't need to manually type that in.

    But I agree it's largely a clamp-down on (mostly agent-based) LLM use.

    But also, it's a big project without BDFL. So this is the policy that ultimately got agreed on. Fully banning wasn't accepted and fully liberal wasn't accepted. This policy is the compromise between both sides

    💬 1🔄 0⭐ 0
  • Aug 11, 2026, 12:47 PM

    @diondokter @zeenix

    > It also leaves room for (private) LLM review

    That's the other part. It explicitly allows private LLM usage. The Rust project is not Apple, they don't have the means to tell people what they do privately on their own computers and definitely not the right :)

    > This policy is the compromise between both sides

    I don't see where the compromise is. My guess is rather that the pro-LLM side just gave up.

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0