Bob Brown

> Also vscode please stop asking me to provide feedback on the extension every time I open a C++ file, this is the only feedback I'll provide :) I'm sorry...

I'm sorry I don't have an ETA for this feature right now. When it is added to a milestone/project, that means we have a target date set for it.

I believe what you are seeing is the debugger trying to step into a source file that you don't have a copy of on your PC. It should be ok...

There is already a list of headers for the add missing include feature. It's possible it could be used for this purpose too. It doesn't have all the new headers...

Support for mac frameworks was added to CMake Tools a while ago. https://github.com/microsoft/vscode-cmake-tools/pull/3247. Though it does require a recent version of CMake. Setting a mac framework path in the include...

The IntelliSense should allow for frameworks directories to be added to the normal include directories. I believe CMake Tools does this because there was a limitation of the API it...

> no body want do this， people want cmake-tools auto config by provider Yes, we understand that. @Colengms knows how to fix this but was giving you a temporary workaround...

> > [@debugee](https://github.com/debugee) You can run C/C++: Log Diagnostics to see if the framework paths are correctly picked up as framework paths instead of normal include paths. After switching to...

`restrict` isn't a standard C++ keyword. Is it a language extension or defined somewhere else? You can try adding it to the list of `defines` in your configuration in `c_cpp_properties.json`...

We support C as well. But as far as I'm aware `restrict` isn't a keyword in C either. The option I suggested also works for C.