@BartOtten There’s no reason except my incompetence. The code was written early in my Elixir journey. At the time my mindset was that use could be doing anything, and it’s in the test code so not released and therefore I don’t need to worry about understanding what it’s doing, or how it works, I just need to know that my tests run. I interpreted async: as a flag, and the tests ran fine. Of course I copied the pattern many times…
The issue is that when I upgraded to 1.18.x my code simply broke, and the message was not especially helpful in tracking down what was wrong. Maybe the macro should insist on a :true or :false value? It is off putting when a minor release breaks your “working” (albeit poor) code in non obvious ways.
