Dave Abrahams

...and now I see there's a note about invocation at the very bottom of the README; if I've taken the trouble to read through the whole implementation I might find...

Need to read your comment, but I created this which I thought you might find useful as a getting started guide: https://gist.github.com/dabrahams/d8d44126a6472e5c3308ffa778c55ddd

Ah, well thanks, but I think I was just wrong to use "c++"; as the list I referenced shows, it's "cpp". Point is, using that will not produce the intended...

Latest updates to https://gist.github.com/dabrahams/d8d44126a6472e5c3308ffa778c55ddd might make a good foundation for a new README, if you make it less language-centric. Cheers!

I get what you're saying; I suggest we both give the idea and your concern some time to bang around in our brains before you decide. It's definitely a different...

I do like the idea of being explicit for clobbering, but I fear I'm going to be, like, 99.9% appending. So I guess another option might be to make auto-append...

Is it not the case that when you create a macro, you usually know whether it's intended to be primarily appended-to or clobbered? I'm suggest that it might be better...

Well, it [appears](https://github.com/dabrahams/gha-setup-swift/actions/runs/8382100945/job/22955147910#step:6:217) we can have the same problem even with the installation order reversed. I'm giving up on this action; feel free to discard my PRs if you want.

FYI, `C:\mingw64\`… is also taking precedence.

The tip of [this branch](https://github.com/hylo-lang/Swifty-LLVM/tree/reduction) contains further diagnostics in `.github/workflows/test.yml`