Nathan Ridge

Oh, whoops, we have to smuggle the `:` past the YAML syntax of the config file. Single quotes seems to do it: ```yaml CompileFlags: Add: ['/std:c++23'] ```

Hmm, then I'm afraid I'm out of ideas for now. Anyways, there are two steps to solving this: 1. Figure out what command-line flags need to be passed to `clang-cl`...

> clang-cl can compile it with flag `-std:c++latest` 😄 Another flags are not supported as I mentioned earlier. My apologies, I misunderstood. So it is a clangd problem then, that...

Let's keep it open. It might be a duplicate of #527, but I'm not sure since the description of #527 talks about **transferring** compile commands specifically (the operation that happens...

@KartikAiyer `c++latest` is a Windows thing (it's an MSVC compiler flag which clang's MSVC-compatibility driver, `clang-cl`, also supports). It's not applicable to other platforms like Mac. The most likely issue...

> If I go to the definition of the `` it is comming from `/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/bit` Ok, so this is libc++. (The version cannot be determined from the path in this...

> I have a cross-compiled project where I was trying to get standard header path extraction to work. In my environment, `arm-none-eabi-gcc` is resolved by default to `/usr/sbin/arm-none-eabi-gcc`. > >...

Ah, I see. Currently, the matching of the driver's path against the `--query-driver` pattern is purely string-based, with no filesystem operations like symbolic link resolution involved.

Maybe I'm missing something, but your observations make sense to me: if your driver's actual path is `/usr/sbin/arm-none-eabi-gcc`, then: * it matches the pattern `/usr/sbin/arm-none-eabi-gcc` * it matches the pattern...

As a vscode user, my approach is to specify `--query-driver` only on a per-project basis. I'll either just hard-code the path (no globs), or for a more portable approach, have...