Rollup of 11 pull requests#156473
Conversation
- Use matches!() macro instead of match in item_kind.rs - Remove unnecessary derefs and simplify Option mapping in validator.rs - Replace clone() on Copy type with *id - Fix doc comment indentation - Remove redundant tuple parens in tests.rs - Remove needless borrow and closure in main.rs
- Add a check while trying to resolve parents, so that for links like
[`::unresolved::path`], rustdoc will say:
"no item named `unresolved` in scope"
instead of:
"no item named `` in scope"
- Update corresponding test
replace TODO with FIXME
document move expression lowering flow
This was an issue for old ptx ISA versions. Those are not supported by rustc anymore
- Check whether an unresolved path is in fact invalid. This prevents rustdoc from emitting nonsensical diagnostics like: - "no item named `std:` in scope" - "no item named `` in scope" Instead rustdoc will now say "has invalid path separator" (the same message from `MalformedGenerics::InvalidPathSeparator`) This is done by checking whether each path segment is empty or contains extra ":" after it's been split by the path separator "::". - Add a dedicated test `tests/rustdoc-ui/intra-doc/invalid-path-separator.rs` for this. - Some unrelated test snapshots have been updated because of this new check.
Replace a hardcoded constant with `mem::variant_count` to keep in-sync with the `ResolutionFailure` enum.
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
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 64a965e (parent) -> aa31d6d (this PR) Test differencesShow 136 test diffsStage 1
Stage 2
Additionally, 92 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard aa31d6d8020dcb7c6e6635648d1ca2bc18caf059 --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 |
|
📌 Perf builds for each rolled up PR:
previous master: 64a965e901 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (aa31d6d): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 2.9%, secondary -2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 3.0%, secondary 15.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 498.063s -> 501.063s (0.60%) |
Successful merges:
move($expr)) #155023 (Introduce move expressions (move($expr)) )intrinsic::raw_eqin MIR when possible #156429 (Simplifyintrinsic::raw_eqin MIR when possible)drop_gluejust unsize and call the slice version #155184 ( Have arrays'drop_gluejust unsize and call the slice version)broken_intra_doc_links#156022 (rustdoc: Fix cosmetic issues when reporting unresolved paths inbroken_intra_doc_links)returnaddressintrinsic return type #156461 (LLVM 23: Specifyreturnaddressintrinsic return type)CheckAttrVisitorso rustfmt can format it. #156466 (RefactorCheckAttrVisitorso rustfmt can format it.)r? @ghost
Create a similar rollup