Rollup of 6 pull requests#158043
Conversation
Document the built-in `must_use` attribute in the standard library using the `#[doc(attribute = "...")]` mechanism, following the existing `keyword_docs.rs` pattern.
To get a `LintVec` for a lint pass we sometimes use `get_lints` and sometimes use `lint_vec`. It would be nice to only have one, but doing that is tricky. In the meantime, this commit makes the naming more consistent. - By always using the name `get_lints` for the methods that take `self`. - By always using the name `lint_vec` for the methods that have no parameters.
These are both types that impl `LintPass` but in a degenerate way: only the `lint_vec` method is ever used. This commit changes them to just be a `lint_vec` function in an appropriately-named module. The commit also removes the use of `HardwiredLints` in `late_lint_crate`, which had no effect because all the `HardwiredLints::check_*` methods were no-ops.
- Document which pass each lint belongs to. - Make the lint ordering consistent. - Add (commented out) `SYMBOL_INTERN_STRING_LITERAL`, which was missing, with an explanation of why it's disabled.
And fix a few cases it catches.
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
…fonthey,saethlin make more slice mutable ref getters rustc_no_writable This makes https://rust.godbolt.org/z/TreEYqfW8 work. Cc @quiode @JoJoDeveloping
…ross Document that destructors in running threads are not run on program exit It's my understanding that, when a Rust program's main thread terminates and thereby causes any still-running threads to be shut down, destructors are not run for the shut-down threads; however, the documentation doesn't seem to come out and say that explicitly anywhere. This PR therefore adds an explicit statement about this to the `std::thread` docs. If I am mistaken and destructors *are* run, that's worth documenting explicitly, too.
… r=GuillaumeGomez,ehuss Add documentation for the `must_use` attribute Document the built-in `must_use` attribute in the standard library using the `#[doc(attribute = "...")]` mechanism, following the existing `keyword_docs.rs` pattern. Part of rust-lang#157604. r? @GuillaumeGomez Tested with `./x test library/std --doc`.
…s-SoftLints, r=Urgau Simplify `HardwiredLints` and `SoftLints` Details in individual commits. r? @Urgau
…cies, r=marcoieni Pin dependencies This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/checkout](https://redirect.github.com/actions/checkout) | action | pinDigest | → `93cb6ef` | | [actions/download-artifact](https://redirect.github.com/actions/download-artifact) | action | pinDigest | → `3e5f45b` | | [actions/upload-artifact](https://redirect.github.com/actions/upload-artifact) | action | pinDigest | → `043fb46` | --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/rust-lang/rust). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMTkuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIxOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
…iteral-rustdoc, r=Urgau Enable `symbol_intern_string_literal` lint for rustdoc Details in individual commits. r? @Urgau
This comment has been minimized.
This comment has been minimized.
Rollup of 6 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple try-job: x86_64-mingw-1 try-job: i686-msvc-2
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 693b3e4c6e In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 693b3e4 (parent) -> c1b22f4 (this PR) Test differencesShow 718 test diffs718 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard c1b22f44c3f30e186b829de95f59740c3a690aba --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (c1b22f4): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 2.3%, secondary 0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -7.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 522.375s -> 523.599s (0.23%) |
Successful merges:
must_useattribute #157957 (Add documentation for themust_useattribute)HardwiredLintsandSoftLints#158006 (SimplifyHardwiredLintsandSoftLints)symbol_intern_string_literallint for rustdoc #158025 (Enablesymbol_intern_string_literallint for rustdoc)r? @ghost
Create a similar rollup