boocs

Actually it's better to make sure the setting is off so it doesn't fallback to tag parser. ``` C_Cpp.intelliSenseEngine should be set to default C_Cpp.intelliSenseEngineFallback should be set to disabled...

I've released 3.3.0 with new strict path setting behavior. Basically don't use the strict path extension setting anymore. Uncheck and reset your project (Generate Project Files) I've also done a...

Even though I recommend against it I have another Mac(non M1) that says /usr/bin/clang worked for them. So you can also try enabling the extension's strict setting and putting /usr/bin/clang...

I rented a cloud M1 Mac and just changing the compile commands path to /usr/bin/clang made Intellisense work. Strange behavior but hope that helps! I'll probably change the way my...

New update makes the compiler path setup easier. I tested it on an M1 Mac and changed my compiler path to /usr/bin/clang++ and it worked.

Yep I noticed it slow to start as well but the cloud M1 Mac I rented it only took ~4 minutes. But I'll retest once I get my cloud mac...

Can you also type '/usr/bin/clang++ -v' on the console again to see what version it goes to?

Hmm for some reason my cloud mac got upgraded to XCode 14, but yes it also does the same query clang defaults slowness ( but also works after). On the...

Some things to try: Make sure you can build successfully first with the 'Editor' suffix config like so:  This is a VSCode Build Task. TestFps is the project name...

I do have a compiler path setting in my extension but the includePath making it work is weird. It would mean that it's not using the compile commands file for...