Add another note about rust-analyzer

Author: 9SMTM6

.gitignore

@@ -2,6 +2,7 @@ target
 dist
 site/public/*
 .vscode
+!examples/wasm_threads/.vscode
 .idea/
 .DS_Store
 /vendor

examples/wasm_threads/.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+    // The build-std flag requires an explicit target.
+    // This breaks the usual rust-analyzer setup.
+    // But setting the target manually for the workspace fixes that.
+    // "rust-analyzer.cargo.target": "x86_64-unknown-linux-gnu",
+    "rust-analyzer.cargo.target": "wasm32-unknown-unknown",
+}

examples/wasm_threads/README.md

@@ -42,3 +42,7 @@ If you get errors such as
 > [Chrome] SharedArrayBuffer transfer requires self.crossOriginIsolated.
 
 Then the headers did not set correctly. You can check the response headers on the `/` file in the network tab of the browser developer tools.
+
+## Using rust-analyzer
+
+Since we use the build-std flag in the toolchain file, and that requires an explicit target to be set for compilation etc., this will break rust-analyzer in many setups. This can be solved by specifying an explicit target for the workspace, such as with the provided [config file for vscode](./.vscode/settings.json).