-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 14 pull requests #101295
Rollup of 14 pull requests #101295
Conversation
This makes it consistent with `x.py` as changed in rust-lang#95671 Fixes rust-lang#100459
This is so you can check out an upstream commit in src/llvm-project and have everything just work.
Needed after changes in rust-lang#97513.
Use third person, as it is used for other std documentation.
Walkthrough currently say: ``` rustup target add aarch_64-fuchsia ``` but should say ``` rustup target add aarch64-fuchsia ```
The impl-items list stopped being nested inside a docblock since c1b1d68
The filename differed from the link in SUMMARY.md, causing it to 404.
Add `special_module_name` lint Declaring `lib` as a module is one of the most common beginner mistakes when trying to setup a binary and library target in the same crate. `special_module_name` lints against it, as well as `mod main;` ``` warning: found module declaration for main.rs --> $DIR/special_module_name.rs:4:1 | LL | mod main; | ^^^^^^^^^ | = note: a binary crate cannot be used as library warning: found module declaration for lib.rs --> $DIR/special_module_name.rs:1:1 | LL | mod lib; | ^^^^^^^^ | = note: `#[warn(special_module_name)]` on by default = note: lib.rs is the root of this crate's library target = help: to refer to it from other targets, use the library's name as the path ``` Note that the help message is not the best in that it doesn't provide an example of an import path (`the_actual_crate_name::`), and doesn't check whether the current file is part of a library/binary target to provide more specific error messages. I'm not sure where this lint would have to be run to access that information.
…lacrum Use `getuid` to check instead of `USER` env var in rustbuild This makes it consistent with `x.py` as changed in rust-lang#95671 Fixes rust-lang#100459
…mulacrum bootstrap: Add llvm-has-rust-patches target option This is so you can check out an upstream commit in src/llvm-project and have everything just work. This simplifies the logic in `is_rust_llvm` a bit; it doesn't need to check for download-ci-llvm because we would have already errored if both that and llvm-config were specified on the host platform.
Make docs formulation more consistent for NonZero{int} Use third person, as it is used for other `std` documentation.
…re-whitespace, r=notriddle Remove unneeded where whitespace It fixes these two bugs: ![Screenshot from 2022-08-31 18-14-40](https://user-images.githubusercontent.com/3050060/187727950-94657419-abfa-454c-9d27-004280fbcb45.png) ![Screenshot from 2022-08-31 18-14-49](https://user-images.githubusercontent.com/3050060/187727956-21d1b39d-62d7-4e7b-8f6f-631ceda67a19.png) It's a relic from a very old time (this commit: rust-lang@bfd01b7). You can test the result [here](https://rustdoc.crud.net/imperio/remove-unneeded-where-whitespace/lib2/struct.WhereWhitespace.html). cc `````````@jsha````````` r? `````````@notriddle`````````
Fix bad target name in Walkthrough Walkthrough currently say: ``` rustup target add aarch_64-fuchsia ``` but should say ``` rustup target add aarch64-fuchsia ```
…re-css, r=jsha rustdoc: remove unused `.docblock .impl-items` CSS The impl-items list stopped being nested inside a docblock since c1b1d68
… r=tmandry Fixes/adjustments to Fuchsia doc walkthrough Small fixes/adjustments missed during rust-lang#100927
…lett Update outdated comment about output capturing in print_to.
…_impl, r=notriddle Fix doc_auto_cfg for impl blocks in different modules with different `cfg` Fixes rust-lang#101129. Just like reexports, impl blocks don't necessarily share the same "space" as the item they implement so we need to merge attributes from its parents as well. r? `@notriddle`
…-when-closure-is-already-marked-as-move, r=oli-obk Do not suggest adding `move` to closure when `move` is already used Fixes rust-lang#101227
@bors r+ rollup=never p=14 |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 10706d62da In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
📌 Perf builds for each rolled up PR: previous master: 2e35f954ad In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (10706d6): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
The regressions are all in the doc profile. One test case I looked at showed a 734% increase to the @rust-timer build d3191247b17a806e5df88fb740ba418926f29e27 |
Queued d3191247b17a806e5df88fb740ba418926f29e27 with parent 2e35f95, future comparison URL. |
Finished benchmarking commit (d3191247b17a806e5df88fb740ba418926f29e27): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
@GuillaumeGomez @notriddle it indeed looks like #101279 is responsible for these regressions. |
Yes, a bugfix where some |
Since this was for a bug fix and we tend to be a bit more lenient with rustdoc regressions, I'll go ahead and mark this as triaged. @rustbot label +perf-regression-triaged |
Successful merges:
special_module_name
lint #94467 (Addspecial_module_name
lint)getuid
to check instead ofUSER
env var in rustbuild #100852 (Usegetuid
to check instead ofUSER
env var in rustbuild).docblock .impl-items
CSS #101254 (rustdoc: remove unused.docblock .impl-items
CSS)cfg
#101279 (Fix doc_auto_cfg for impl blocks in different modules with differentcfg
)move
to closure whenmove
is already used #101285 (Do not suggest addingmove
to closure whenmove
is already used).content table td:first-child > a
#101292 (rustdoc: remove unneeded CSS.content table td:first-child > a
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup