-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Document dist components we ship #141386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
cc @Mark-Simulacrum: you might be someone who have some clues about what the purposes of the (less obvious) dist components we ship are... Are there any docs or historical discussions that you know of for them? |
Historical discussions are probably just in the PR(s) that landed them if anywhere. I can try to get a PR out for the steps in dist.rs in bootstrap having doc comments perhaps, as a starting point? Unless we want the docs to live elsewhere -- depends I guess how much this is externally guaranteed vs. useful for ourselves. |
Yeah, part of this is I don't actually know what we do guarantee, be it external or internal (often by implicit assumptions). For instance, I think miri depends on rustc-dev, so even if it's technically "internal" it's still logistically depended upon. cc @RalfJung is that description accurate for miri? |
I don't know what you mean by "internal" vs "external", but all tools that use the rustc driver depend on rustc-dev -- we have some of those in-tree (Miri, clippy), and there's plenty more out-of-tree (e.g. all the verification tools, minirust, and I guess klint as well). |
I don't think the distinction matters that much tbh, since if the |
The components are lightly documented at https://rust-lang.github.io/rustup/concepts/components.html. Things like llvm-tools was accidentally "stabilized" due to a bug, and how people were using it. There are more questions and context in #85658, but so far the compiler team has not been able to answer the questions about it. |
Uh oh!
There was an error while loading. Please reload this page.
E.g. #138647.
We should document:
The text was updated successfully, but these errors were encountered: