Move rustfmt binariy crates to workspace #4002
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After I separated rustfmt into multiple crates, I realized that cargo builds rustfmt-core twice: for rustfmt-core itself and for rustfmt-nightly (the root crate that holds binaries). This duplication is not ideal during development.
The goal of this PR is to mitigate the overhead by moving binaries under the
rustfmt-core
workspace. The root Cargo.toml works as a shim to the actual binary crate, which is necessary for the rustc repository.The downside is that we now need to keep the root Cargo.toml in sync with rustfmt-core/rustfmt-bin/Cargo.toml.