Use the query vtable in query_feed plumbing#151853
Use the query vtable in query_feed plumbing#151853rust-bors[bot] merged 1 commit intorust-lang:mainfrom
query_feed plumbing#151853Conversation
|
rustbot has assigned @jdonszelmann. Use |
|
@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.
Use the query vtable in `query_feed` plumbing
This comment has been minimized.
This comment has been minimized.
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@bors try cancel |
|
Try build cancelled. Cancelled workflows: |
|
@bors try |
This comment has been minimized.
This comment has been minimized.
Use the query vtable in `query_feed` plumbing
|
💥 Test timed out after |
|
@bors try |
This comment has been minimized.
This comment has been minimized.
Use the query vtable in `query_feed` plumbing
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7238d58): comparison URL. Overall result: ❌✅ regressions and improvements - no action neededBenchmarking 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. @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 (primary -1.5%, secondary -0.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 0.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 474.712s -> 474.274s (-0.09%) |
|
Perf results look noisy/bimodal, nothing remarkable that I can see. @rustbot ready |
|
Not quite comfortable with the internals here, even though it looks correct. Maybe r? @oli-obk ? I think you worked on query feeding no? |
|
|
|
Ah, wonderful. That's much better. I def wasn't looking at the larger picture, which I should have been doing @bors r+ |
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 79a1e77 (parent) -> 55407b8 (this PR) Test differencesShow 226 test diffs226 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 55407b8cdb1457c62e0c852f5b53a9cf63ec4e1b --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 (55407b8): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -2.5%, secondary 1.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 2.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 473.794s -> 471.991s (-0.38%) |
The
query_feedfunction needs to be able to do two important things with (erased) query values: hash them, and debug-print them.Both of those are things that the query's vtable already knows how to do. So by passing in a vtable to
query_feed, we can give it a nicer signature, avoid having to unerase values in the function itself, and clean up some caller-side code as well.