Ilya Biryukov

The issue is that C++20 adds [rewritten candidates](https://en.cppreference.com/w/cpp/language/overload_resolution) with reversed parameters. These sometimes happen to be ambiguous with themselves. In particular, in this case for `operator ==(const Base*/*this*/, const Derived&)`...

Another workaround is to pass `-pch-storage=memory` to clangd and avoid creating those temporary files completely. Only works if you have lots of memory to spare for clangd.

Changing those affects other programs too, though, e.g. text editors that start clangd. So I agree a separate flag/env var that gives a more fine-grained control would be useful.

Hm, I can see how .clangd is more suitable in most cases, e.g. build results normally live near the source dir, they're large and there's normally enough space to hold...

In fact, this is already implemented. In VSCode it's off by default, you'll need to set`"editor.formatOnType": false`.

However, it does not do one of the suggested examples: ``` // Foo ^ ``` Will get turned into ``` // Foo ^ ``` In a similar situation inside the...

Great idea! We could potentially get a better "switch header-source" for free while implementing this feature too.

This is very raw: tests fail, an approach to codegen needs to be updated, the documentation and PR description needs to be improved. Still posting this to get early feedback...

> Did you mean `Check` phase? 🤦 I did, thanks for pointing that out.

I've picked this up again and it's shaping up now, should be close to something I'd like to land. In particular, we now use the code generator from Clang rather...