@zenkat @dngrs (again, in the open source library-with-multiple-clients world, this would just never be an option for me; even if I could just sledgehammer my *own* code with an LLM and it worked perfectly, we still need a migration glide path for all of our users, many of whom are similarly constrained in their ability to apply LLMs for various reasons)

@zenkat @dngrs second, this is another opportunity for the Waluigi effect or some paperclip optimizing to creep in. I was speaking to a much more LLM-positive friend recently who did something similar with a refactoring tool at their job, and they noticed that it did some of the migration incorrectly, but it was about to pass QA checks. the way it was going to pass was that the LLM figured out it was cheaper to edit the test suite to invert the assertions than to fix the code