https://discourse.llvm.org/t/rfc-llvm-ai-tool-policy-human-in-the-loop/89159>We don't need more contributors who aren't programmers to contribute code
>>107717547>https://discourse.llvm.org/t/rfc-llvm-ai-tool-policy-human-in-the-loop/89159>vibecoded LLVMwhat the absolute fuck?wtf does he mean>"most contributors (or at least the subset with the resources and interest in attending this round table in person) are interested in using LLM assistance to increase their productivity, and I really do want to enable them to do so"its over, right?msft tier of code quality coming to everyones fuckken compiler backend, right?fucking kill me, everything is retarded
>>107717565This is bait. The policy in the first post is all about banning vibecoding.> there must be a human in the loop. Contributors must read and review all LLM-generated code or text before they ask other project members to review it.> they should be able to answer questions about their work during review.> be transparent and label contributions thatcontain substantial amounts of tool-generated content.AI agents are also affected.> bans agents that take action in our digital spaces without human approval
>>107717547they'll ban AI but they won't ban the cockroach horde of Indians who are using AI to submit "patches" lolalso>they should be able to answer questions about their workjust ask the AI to answer the questions and then rewrite the response to be less AI-sounding
>>107718346yeah no sure, vibecoding properbut i extend the definition to """proper prompting""" because the result will be substandard shit ass code.especially the bar is "to be able to explain code, and label code thats heavily generated as such">chud gpt, write me xyz, but be extra explicit in your naming conventions and comments so that i can explain the code only by reading theseboom. maintainers now need to audit every piece of contributed code like if it was an oral fukken exam.decision taken by the few ai-retard zealots that could make it to the "round table meeting" prolly in some casino in vegas or something like that. like the rest of the world doesnt exist, or that everyone has time to infiltrate every decisionmaking process in the foss worldfuck em, ill run an older version of my compiler stack. its only a matter of time until llvm fucking crashes and burns and then theyll go back to sane practices, even if it takes quite literally everybody to start yelling at them bc theyre breaking everyone's shit
>>107718398>its only a matter of time until llvm fucking crashes and burns and then theyll go back to sane practicesthey are already doing insane practices and no one is doing anything about it lol
>>107718441because it still works to a satisfactory degreehopefully the ai-retards are gonna help change that because i like certain gcc-exclusive featureswhat i dont like is the idea that llvm can cripple all of that because theres a bunch of fucking mongoloid retards who havent been beaten often enough in their youth at the helm of the thingthis really pisses me off, im reliant on this shitsaving grace: im not reliant on updates for my stack, i can just stick with what works for me, indefinitely
