Commit Graph

5 Commits

Author SHA1 Message Date
Daira-Emma Hopwood 3e5e4f30cd 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 23:25:55 +01:00
Andrew Arnott bb06f84f65
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 08:14:39 -06:00
Jack Grigg 17ce9302a2 Add `zcash_unstable` to `RUSTFLAGS` for VS Code
Necessary for the `--all-features` to work, allowing all code to be
compiled by `rust-analyzer`.
2024-01-26 19:52:58 +00:00
Andrew Arnott 1804647112
Update .vscode/settings.json
Co-authored-by: str4d <thestr4d@gmail.com>
2024-01-04 11:44:17 -07:00
Andrew Arnott 976a5e0366
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 14:22:03 -07:00