Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upEnsure that SxS installation of crates from multiple compilers works reliably #29560
Comments
steveklabnik
added
the
A-build
label
Nov 4, 2015
This comment has been minimized.
This comment has been minimized.
|
Triage: dunno if @brson gave this any thought yet exactly |
steveklabnik
added
the
T-compiler
label
Mar 8, 2017
Mark-Simulacrum
added
the
C-tracking-issue
label
Jul 24, 2017
This comment has been minimized.
This comment has been minimized.
|
Triage: it seems packaging is working well, and brson doesn't work on Rust anymore. I'm going to close this. |
steveklabnik
closed this
Mar 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
brson commentedNov 4, 2015
For SxS installations of arbitrary Rust compilers, there will be multiple copies of the standard library residing in the same path. Without care, rustc will see them as duplicates.
Neither @alexcrichton or I am confident that the current crate resolver correctly rejects crates that weren't generated by the same compiler, though we suspect it works correctly in most scenarios.
Tightening this up further could have negative implications for e.g. a distributed Cargo cache, depending on how strict rustc is about rejecting crates it didn't produce.
I'm not sure how real this problem is but probably needs some thought.
https://internals.rust-lang.org/t/perfecting-rust-packaging-the-plan/2767