build-std: explicit dependencies#3875
Open
davidtwco wants to merge 33 commits intorust-lang:masterfrom
Open
Conversation
This was referenced Oct 31, 2025
Merged
davidtwco
added
T-cargo
clarfonthey
reviewed
Oct 31, 2025
clarfonthey
reviewed
Oct 31, 2025
clarfonthey
reviewed
Oct 31, 2025
clarfonthey
reviewed
Oct 31, 2025
clarfonthey
reviewed
Oct 31, 2025
This was referenced Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
epage
reviewed
Oct 31, 2025
Veykril
reviewed
Nov 1, 2025
epage
reviewed
Jan 7, 2026
epage
reviewed
Jan 7, 2026
epage
reviewed
Jan 7, 2026
epage
reviewed
Jan 11, 2026
Contributor
|
@rfcbot fcp concern redundant-no-std See #3875 (comment) |
Contributor
|
@rfcbot fcp resolve redundant-no-std |
epage
reviewed
Mar 3, 2026
Comment on lines
+1106
to
+1114
| ### Should we support `build-dependencies`? | ||
| [unresolved-build-deps]: #should-we-support-build-dependencies | ||
|
|
||
| Allowing `builtin` dependencies to be used in `dependencies` and | ||
| `dev-dependencies` but not in `build-dependencies` is an inconsistency. | ||
|
|
||
| However, supporting `builtin` dependencies in `build-dependencies` would permit | ||
| no-std build scripts. It is unclear whether supporting no-std build scripts | ||
| would be desirable. |
Contributor
There was a problem hiding this comment.
We should call out that the current behavior is a safe default because to change it is to turn an error case into a success case, making this a two-way door
epage
reviewed
Mar 10, 2026
Comment on lines
+1118
to
+1124
| ### Should `cargo metadata` include the standard library's dependencies? | ||
| [unresolved-cargo-metadata]: #should-cargo-metadata-include-the-standard-librarys-dependencies | ||
|
|
||
| `cargo metadata` is used by tools like rust-analyzer to determine the entire | ||
| crate graph and would benefit from knowledge of the standard library's | ||
| dependencies, but this leaks internal details of the standard library and is | ||
| counter to the intent behind opaque dependencies. |
Contributor
There was a problem hiding this comment.
Can we expand that the main concern for doing this is compatibility but
cargo pkgidandcargo build --message-formatwill unconditionally use the new pkgid speccargo_metadatadoes not currently parse the pkgid spec so this won't break all users- this will also show up in the source which is still opaque and
cargo_metadatadoes not parse
So this is only a problem for users who are parsing pkgid specs using cargo-util-schemas or their own parser. The scope of that is likely small enough to not be too disruptive.
There was a problem hiding this comment.
Crater uses cargo-util-schemas to parse pkgid specs1.
Edit: Though failing to parse std internal dependencies shouldn't be a problem for crater.
Footnotes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
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.
Allow users to add explicit dependencies on standard library crates in the
Cargo.toml. This enables Cargo to determine which standard library crates are required by the crate graph withoutbuild-std-cratesbeing set and for different crates to require different standard library crates.This RFC is is part of the build-std project goal and a series of build-std RFCs:
build-std="always"(build-std: always #3874)build-std="compatible"(RFC not opened yet)build-std="match-profile"(RFC not opened yet)There is also a Zulip channel where you can ask questions about any of the build-std RFCs. This series of RFCs was drafted over many months with the help of stakeholders from many Rust project teams, we thank them for their help!
There are some details that have been noted as being worth mentioning in any eventual tracking issues:
FCP
Rendered