diff options
| author | huntc <[email protected]> | 2021-12-09 10:40:03 +1100 |
|---|---|---|
| committer | huntc <[email protected]> | 2021-12-09 10:40:03 +1100 |
| commit | 990d2330dbcec71bf72bdc116c390181f8d995cc (patch) | |
| tree | a5bbc83c1f7a9cbcc61ff5fdce21c4ebaada194c /.vscode/settings.json | |
| parent | 4eb9f0f3aebfa7b1d72830da2241b2a8b7ca139f (diff) | |
Rust Analyzer documentation
Intends to clarify how to make Embassy usable from within Visual Studio Code by assuming the presence of the Rust Analyzer.
Note that IntelliJ does not support the Rust Analyzer, so an open question remains as to the whether this is a good move. If it turns out not to be a good move then we should still look at clarifying the use of a workspace file.
Diffstat (limited to '.vscode/settings.json')
| -rw-r--r-- | .vscode/settings.json | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/.vscode/settings.json b/.vscode/settings.json index a35be8054..b229f7eb6 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json | |||
| @@ -16,7 +16,8 @@ | |||
| 16 | //"embassy-net/pool-16", | 16 | //"embassy-net/pool-16", |
| 17 | ], | 17 | ], |
| 18 | "rust-analyzer.linkedProjects": [ | 18 | "rust-analyzer.linkedProjects": [ |
| 19 | "examples/stm32f1/Cargo.toml" | 19 | // Declare for the target you wish to develop |
| 20 | "examples/nrf/Cargo.toml" | ||
| 20 | ], | 21 | ], |
| 21 | "rust-analyzer.procMacro.enable": true, | 22 | "rust-analyzer.procMacro.enable": true, |
| 22 | "rust-analyzer.cargo.runBuildScripts": true, | 23 | "rust-analyzer.cargo.runBuildScripts": true, |