-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
namespace "std" has no member "thread" #952
Comments
what does gcc report as the default include path when you run |
Also, please make sure you set the |
Let us know if the suggestions above were unable to help you resolve your issue. |
@alitoufighi The "no type named" message doesn't come from our extension. Do you have another one installed? |
VSCode Extensions > C/C++ > Extension Settings > C_CPP: Intelli Sense Engine > Set to "Tag Parser" This solved the problem for me. |
Using the "Tag Parser" engine will disable IntelliSense squiggles and remove semantic matches in the autocomplete list. It's not recommended unless you are using a specialized compiler that is incompatible with MSVC or GCC/Clang. As this issue is quite dated, the information is old. You should use |
If you are having issues with red squiggles or getting the extension configured at all, please open a new issue and we'd be happy to help you troubleshoot it. |
When I use the std::thread in my code, there will be an error like this:
![_0 un xqx 2 qx22cruy442](https://user-images.githubusercontent.com/11624776/29011209-bf15b422-7b63-11e7-920b-8a46b1a72348.png)
But I can click "go to the declaration" on it, and jump to file "thread" and see the class definiton of thread:
![_2 1o 8d xkl3 ajco pbd4](https://user-images.githubusercontent.com/11624776/29011253-19c46bac-7b64-11e7-9af4-b58b646a093a.png)
I use cygwin environment on Windows, here is my include_path in
c_cpp_properties.json
:When I build with
-std=c++11
, I can run the program normally, I just can't eliminate the warning.Did I miss some path? Or should I add some macro definition in the
.json
file?The text was updated successfully, but these errors were encountered: