zec
/
librustzcash
mirror of https://github.com/zcash/librustzcash.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
librustzcash/.vscode/settings.json

5 lines
117 B
JSON
Raw Normal View History

Enable unstable features when editing in VS Code This improves the editing experience by 'enabling' all the code that otherwise is turned off because of the `unstable` flag.
2023-12-16 13:14:28 -08:00
{
Tell rust-analyzer to compile using stable, because the Rust version from `rust-toolchain.toml` is too old for the current proc-macros protocol (specifically, the `--keep-going` flag was not stable in Rust 1.70, as can be verified by `cargo +1.70.0 check --keep-going`). This works around https://github.com/rust-lang/rust-analyzer/issues/17662 , and very likely future problems, because the rust-analyzer devs are quite aggressive in depending on recent versions: "by policy we don't make any attempts at supporting more than the last couple of stable releases" according to https://github.com/rust-lang/rust-analyzer/issues/17662#issuecomment-2242265513 . The toolchain we select in `rust-toolchain.toml` often lags behind that intentionally, because we want to verify that we build with our MSRV. Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
2024-07-28 15:25:55 -07:00
"rust-analyzer.cargo.features": "all",
"rust-analyzer.server.extraEnv": { "RUSTUP_TOOLCHAIN": "stable" }
Drop orchard unstable flag from VS Code settings This setting is no longer required, and its presence greatly increases build and test times while using VS Code extensions for rust because inconsistent settings are used, defeating the rust build cache.
2024-06-18 07:14:39 -07:00
}