-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Add note about change in bootstrap defaults #110663
Conversation
Hmm, this seems like it would have bitten me, because I do list |
Yeah, that seems plausible. It seems pretty likely that we'll build it implicitly in some cases but not others. I'm not sure how to better phrase this -- in general I think I would recommend that you and others do explicitly add rustdoc to the tools list if you want it, since otherwise future iterations might e.g. error out saying "well, not asked for, refusing to build" or similar. (Particularly if/when we start looking into optimizing our CI, and e.g., cross-compiling parts from other builders or similar). |
Ah wait I misunderstood, those are tests failing for some crate being built by the new toolchain, not for our own test suite. Ok, that seems unavoidable if rustdoc's not installed. I think we can still have an easier transition though — @dtolnay would it be enough for |
I think the change in defaults is reasonable. Rustdoc is a tool, we have a list of tools, if you don't include it there you're signaling you don't need/want it. |
Rustdoc is a privileged tool though -- normally bundled with rustc rather than its own component. Distros keep them together too, at least on Debian and Fedora/RHEL, so I think it will be surprising to have to list it explicitly. Nevertheless, a compat note for what we already shipped seems appropriate, and I guess it doesn't matter if we nail down the specifics in that note. @bors r+ rollup |
…=cuviper Add note about change in bootstrap defaults Not a huge fan of the proposed wording, open to changes in that. Per rust-lang#106886 (comment). cc `@jonhoo` r? `@cuviper` perhaps?
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#110661 (rustdoc: clean up settings.css and settings.js) - rust-lang#110663 (Add note about change in bootstrap defaults) - rust-lang#110664 (stop `x fmt` formatting untracked directories) - rust-lang#110668 (Fix printing native CPU on cross-compiled compiler.) - rust-lang#110689 (Fix grammar in core::hint::unreachable_unchecked() docs) - rust-lang#110700 (Don't infer fn return type to return itself) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Not a huge fan of the proposed wording, open to changes in that.
Per #106886 (comment).
cc @jonhoo
r? @cuviper perhaps?