WebAssembly / WebAssembly/wasi-sdk
MSVC IntelliSense stops working after wasi-sdk-15
Nobody has claimed this yet.
- Dominant language
- CMake
- Stars
- 1.6k
- Forks
- 237
- Avg merge
- 18h 26m
- Merged PRs (30d)
- 5
Description
MSVC C++ IntelliSense gets very confused with recent SDK versions. (Tested with Visual Studio 2019, 2022, and 2022 Preview builds.) Is this perhaps an upstream LLVM 14.0 issue?
(Variants of this issue appear in other MSVC projects that utilize wasi-sysroot but run through MSVC for IntelliSense.)
Steps to reproduce
-
Create empty directory
-
Download latest sysroot release (https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-21/wasi-sysroot-21.0.tar.gz)
-
Extract sysroot into
[directory]\wasi-sysroot -
Create
test.cppwith the following contents:#include <string> int main() { std::string test("hello"); } -
Create
CppProperties.jsonwith the following contents:{ "configurations": [ { "name": "Repro", "includePath": [ "${workspaceRoot}\\wasi-sysroot\\include", "${workspaceRoot}\\wasi-sysroot\\include\\c++\\v1", "${env.INCLUDE}" ], "intelliSenseMode": "windows-msvc-x64" } ] } -
Open Visual Studio > File > Open Folder >
[folder path] -
Observe (after a bit of waiting), Visual Studio shows red squiggles™️on
std::stringusage -
Close Visual Studio
-
Delete
[folder]\.vs -
Edit
CppProperties.jsonand changeintelliSenseModetowindows-clang-x64 -
Open Visual Studio > File > Open Folder >
[folder path] -
Observe (after a bit of waiting), Visual Studio shows no squiggles™️
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided test.cpp and CppProperties.json reproduction using the wasi-sysroot-21 release in Visual Studio. Compare windows-msvc-x64 and windows-clang-x64 IntelliSense behavior, then determine whether the issue is in the SDK/sysroot or upstream LLVM/MSVC before defining a fix and regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100