C++17 types cannot be resolved in Visual Studio 2019

Hey all, 

Seems like there is a bug with c++17 and the new Visual Studio that marks new standard library types (e.g. std::string_view) as unresolved symbols although they present and usable.

6 comments

Hello!

Could you send us a sample solution where this problem happens?

Did you remember to set "C++ Language Standard" to /std:c++17 or /std:c++latest?

0

Hey Igor,

 

I've created a git-repository with the sample. You can find it under the following URL:

https://github.com/yunharla/Snippets/tree/master/Resharper%20Problem

0

This project does not compile, does it? As I said, you need to set "C++ Language Standard" to "ISO C++17 Standard (/std:c++17)".

0

I've added the option for Language Standard to the project. Everything compiles fine but the TextEditor still shows that std::string_view is an unresolved symbol.

Furthermore, when resharper is active Intellisense stops working for declarations using these new types.

I can disable resharper for C++ and everything works as expected. Once I enable resharper, these declarations are displayed as error.

In both cases the code compiles and runs.

0

Sorry, I can't reproduce this on your project - when I set "C++ Language Standard" to /std:c++17. Which versions of R++ and Visual Studio are you using?

0

I'm using the following version:

JetBrains ReSharper Ultimate 2018.3.4 Build 183.0.20190304.43214

0

Please sign in to leave a comment.