docs: say how the pinned toolchain goes wrong quietly - #16
Merged
Conversation
`rust-toolchain.toml` pins the compiler and rustup honours it, but only if the
`cargo` being run is rustup's shim. A `cargo` installed elsewhere and earlier on
`PATH` does not read that file, and if `rustdoc` resolves to a different release
than `cargo` does, the workspace compiles with one compiler while its doctests
run under another:
error[E0514]: found crate `serde` compiled by an incompatible version of rustc
Nothing is wrong with the code, and the message does not say so. CONTRIBUTING.md
now names the failure, gives the two commands that show it, and says what to do.
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
1 participant
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.
docs: say how the pinned toolchain goes wrong quietly
rust-toolchain.tomlpins the compiler and rustup honours it, but only if thecargobeing run is rustup's shim. Acargoinstalled elsewhere and earlier onPATHdoes not read that file, and ifrustdocresolves to a different releasethan
cargodoes, the workspace compiles with one compiler while its doctestsrun under another:
Nothing is wrong with the code, and the message does not say so. CONTRIBUTING.md
now names the failure, gives the two commands that show it, and says what to do.
Rendered from
NDDev-it-com/setup-systems@cf18ed1.https://claude.ai/code/session_011eFMKoUdWcc7Aw9vtMxH2A