You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cargo check etc currently checks all our binaries, which is a lot, because it includes all examples, all doc-tests, and all roundtrip tests. This also makes rust-analyzer slower because of this issue:
One solution would be to split off examples and tests to its own workspace.
They should ideally be under its own folder then, but I'm not sure what that should be called.
Or we use many separate workspaces (one for docs, one for examples, one for tests, etc).
Either way we need to make sure all the workspaces are checked on CI (cargo fmt, cargo cranky, …),
which is annoying, because it may require duplicating Cranky.toml, clippy.toml, etc.
Another approach is to combine all existing binaries into one:
emilk
changed the title
Split off tests and examples to a separate Cargo workspace
Reduce the number of crate binaries in the cargo workspace
Jan 10, 2024
cargo check
etc currently checks all our binaries, which is a lot, because it includes all examples, all doc-tests, and all roundtrip tests. This also makesrust-analyzer
slower because of this issue:docs/code-examples
code-examples
into one binary #4767examples/rust
tests/rust
One solution would be to split off examples and tests to its own workspace.
They should ideally be under its own folder then, but I'm not sure what that should be called.
Or we use many separate workspaces (one for
docs
, one forexamples
, one fortests
, etc).Either way we need to make sure all the workspaces are checked on CI (
cargo fmt
,cargo cranky
, …),which is annoying, because it may require duplicating
Cranky.toml
,clippy.toml
, etc.Another approach is to combine all existing binaries into one:
code-examples
into one binary #4767The text was updated successfully, but these errors were encountered: