-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Rollup of 3 pull requests #142826
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 3 pull requests #142826
Conversation
Also ensure the suggestions are checked, since this will be updated.
Use the same error as other invalid types for `concat_bytes!`, rather than using `ConcatCStrLit` from `concat!`. Also add more information with a note about why this doesn't work, and a suggestion to use a null-terminated byte string instead.
…, r=jdonszelmann Port `#[may_dangle]` to the new attribute system Very similar to rust-lang#142498. This is a part of rust-lang#131229, so r? `@jdonszelmann`
…r-errors expand: Remove some unnecessary generic parameters
…petrochenkov Improve diagnostics for `concat_bytes!` with C string literals Use the same error as other invalid types for `concat_bytes!`, rather than using `ConcatCStrLit` from `concat!`. Also add more information with a note about why this doesn't work, and a suggestion to use a null-terminated byte string instead.
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 6d0c9e2a1c 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 6d0c9e2 (parent) -> ea34650 (this PR) Test differencesShow 8 test diffs8 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard ea34650916887b5075812d0f11c1d3209e7f94ab --output-dir test-dashboard And 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 (ea34650): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@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 (secondary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 7.2%)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: 690.042s -> 691.091s (0.15%) |
Successful merges:
#[may_dangle]
to the new attribute system #142539 (Port#[may_dangle]
to the new attribute system)concat_bytes!
with C string literals #142698 (Improve diagnostics forconcat_bytes!
with C string literals)Failed merges:
#[rustc_pub_transparent]
to the new attribute system #142600 (Port#[rustc_pub_transparent]
to the new attribute system)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup