Comment by audunw

5 hours ago

Would recommend checking out the Zig state of the (tagged) union as well.

https://youtu.be/zwi5b5xSsKA?is=PTjJJjSnVMdRuZag

It may surprise some people here to see that Andrew is warming up to using LLMs to discover bugs (inspired by results from SQLlite) and considers it a tool on the path to getting to bug free software.

> It may surprise some people here to see that Andrew is warming up to using LLMs to discover bugs (inspired by results from SQLlite) and considers it a tool on the path to getting to bug free software.

Someone in the thread below says their bug was closed because of mentioning that they use AI to confirm the bug they had encountered. Is he going to go back and reopen all of those now that he learned what pretty much everyone else already knew?

  • > Someone in the thread below says their bug was closed because of mentioning that they use AI to confirm the bug they had encountered

    I don't know about this particular case, but if I saw someone report a bug and as evidence claim they had X Y and Z LLMs verify it I would be pretty upset. If you're going to use an LLM to make a replication, just do that and give me the replication, don't point to your notoriously error-prone tools as though they lend your report credence.

    It's in a similar vein to people who reply to questions with "well Claude says: <chat transcript dump>"

    • > It's in a similar vein to people who reply to questions with "well Claude says: <chat transcript dump>"

      or substantially worse: "<chat transcript dump>"

    • Human reproductions are notoriously error prone whether ai assisted or not right? I’m not sure what the analogy is between “llms are error prone” and “thoughtlessly copy-pasting something from Claude” is.

      3 replies →

    • I feel very torn as a maintainer on this, since the only way to respond to the increased noise from AI has been to have AI do the research for me to extract all the links and line numbers I used to have to find by hand to explain why the PR needs more effort to be completed. But I also will be highly dismissive of any submitter who just posts AI text without cleaning it up first. It feels hypocritical, but the alternative is that I just can’t respond to most people instead due to limited bandwidth. I mark if something comes directly from the LLM though and to try to express my degree of confidence in its claims.

  • I suspect they can't easily tell the difference between a high quality LLM based contribution and a low quality one.

  • Note the distinction:

    - using the LLM to find (possible) bugs and a human confirms it by testing, reviewing, etc.

    - using the LLM to find and confirm the bug without the human confirming it, just trusts and believes LLM

  • > Is he going to go back and reopen all of those now that he learned what pretty much everyone else already knew?

    In the state of the tagged video he says still not accepting AI submissions until a certain set of preconditions is met. So... No?

  • He specifically says in that presentation that they are open to LLMs helping them get to bug free, but because the language is still in flux, they would rather prioritise bugs users actually find rather than those found by LLMs, essentially with the intent of unblocking people rather than wasting time fixing things that may need to be fixed again or be wasted work come the next update.

  • Shouldn't everybody already know that while using AI to find bugs for oneself is amazingly efficient, using AI to submit bug reports for others is quite the opposite? Burden of verification and all.

    • Exactly, the main issue isn't the LLM creating or confirming the report. Rather, the maintainer has no idea how it was prompted, and the results may be completely wrong. Some LLMs also have a bad habit of trying to please the user, confirming their biases.

  • Nobody refuses penicillin because it came from mold in a dish. If an AI found a cure for a disease, people would ask one question: does it work?

    Bug fixes should get the same treatment. A patch is either correct or it isn't. Projects that ban AI-written fixes outright are asking "who wrote this?" instead of "is this right?", and users live with the bug in the meantime.

    I get why maintainers are fed up. Review time is scarce, and they're drowning in plausible-looking garbage. But that's a problem with low-quality submissions, not with AI as such. Require tests, require a human who vouches for the patch and will answer for it, and ban repeat offenders. Then hold every patch to that same bar, whoever or whatever wrote it.

I personally think using AI is of no problem for certain cases. It is absolutely pissing off when someone tries to generate slops that too verbose to review only to increase the complexity of the codebase meaninglessly.

[flagged]

  • It boggles the mind that people believe anyone that thinks differently from them is automatically utterly stupid.

    Actually, on second thought, it really doesn't. Indoctrination and herd mentality are quite the things.