Colen Garoutte-Carson

Hi @RahulSisondia . Are you able to reproduce this issue with our latest pre-release, 1.19.2? There are some significant changes to how IntelliSense passes are managed and scheduled in 1.19.2....

Hi @AndreyDodonov-EH . I suspect the issue you are seeing is different, as netch80's issue seems related to compiler args and your example doesn't involve compiler args. Looking at your...

Hi @DerNils-git . (Based on my comments here: https://github.com/microsoft/vscode-cpptools/issues/11306#issuecomment-1781924298 ) I see from your logs that the CMake Tools extension is registered as a custom configuration provider and does provide...

Hi @w4133d . It looks like you have the following in your `c_cpp_properties.json`: ``` "configurationProvider": "ms-vscode.cpptools" ``` The C/C++ Extension itself is not a custom configuration provider, so this value...

Hi @gcampbell-msft . This appears to be an old issue. On macOS, the C/C++ extension actually assumes the file system is case-sensitive. My reading of the log diagnostics output above...

Hi @tshcherban . You may be repro'ing a different issue. Most of the comments in this issue are now months old. I would suggest opening a new issue and providing...

It's unclear to me if there is an issue here. The C/C++ Extension does appear to use clang-format/clang-tidy in path IF that is a more recent version than bundled with...

Hi @benvanik . I'm not able to repro this issue. I get the same results with 1.18.5 and 1.19.2. I'm seeing the later behavior from both versions. ``` #include #include...

Aha. I failed to repro because I wasn't using a source name that matches the header's name. Now I can repro the difference. It does appear to be a difference...

Hi @david-29 . Does your code compile when built? Since you're using a `compile_commands.json` file, and an entry was found and used for `t1.cpp` and `t2.cpp` (based on your diagnostics...