Uh oh!
There was an error while loading. Please reload this page.
Abstract AST lowering resolver - #153656
Conversation
petrochenkov
commented
Mar 10, 2026
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Split AST lowering resolver into mutable and readonly parts
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Mar 10, 2026
Finished benchmarking commit (34c6408): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -2.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResults (primary -0.0%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 479.559s -> 479.738s (0.04%) |
petrochenkov
commented
Mar 11, 2026
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Split AST lowering resolver into mutable and readonly parts
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Mar 11, 2026
Finished benchmarking commit (fd90094): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary -3.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -1.8%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.0%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 479.3s -> 481.187s (0.39%) |
6ddfe68 to
8158d7fComparepetrochenkov
commented
Mar 12, 2026
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Split AST lowering resolver into mutable and readonly parts
This comment has been minimized.
This comment has been minimized.
petrochenkov
commented
Mar 18, 2026
The PR description needs some update, the lowering resolver was already abstracted through |
aerooneqq
commented
Mar 18, 2026
@rustbot ready |
petrochenkov
commented
Mar 18, 2026
r=me after squashing commits. |
rustbot
commented
Mar 18, 2026
Reminder, once the PR becomes ready for a review, use |
69f6ab2 to
3656fbfCompareaerooneqq
commented
Mar 18, 2026
@rustbot ready |
petrochenkov
commented
Mar 18, 2026
@bors r+ |
This comment has been minimized.
This comment has been minimized.
Uh oh!
There was an error while loading. Please reload this page.
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 53d60bb (parent) -> fd0c901 (this PR) Test differencesShow 3 test diffs3 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard fd0c901b00ee1e08a250039cdb90258603497e20 --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 |
rust-timer
commented
Mar 18, 2026
Finished benchmarking commit (fd0c901): comparison URL. Overall result: ❌ regressions - 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)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 479.87s -> 481.003s (0.24%) |
…r, r=petrochenkov Abstract AST lowering resolver This PR adds new methods for `ResolverAstLoweringExt` for future use in rust-lang#153489 and abstracts resolver in lowering through generic parameters. > ~This PR splits resolver for AST lowering into two parts: mutable and readonly. This will allow us to use borrowed resolver in rust-lang#153489, when we will not steal but borrow resolver from resolve stage.~ Second step for rust-lang#153489. r? @petrochenkov
Do not modify resolver outputs during lowering Split from #142830 I believe this achieves the same thing as #153656 but in a much simpler way. This PR forces AST->HIR lowering to stop mutating resolver outputs. Instead, it manages a few override maps that only live during lowering and are dropped afterwards. r? @petrochenkov cc @aerooneqq
View all comments
This PR adds new methods for
ResolverAstLoweringExtfor future use in #153489 and abstracts resolver in lowering through generic parameters.Second step for #153489.
r? @petrochenkov