-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 10 pull requests #122735
Rollup of 10 pull requests #122735
Conversation
# Conflicts: # tests/ui/lint/lint-qualification.stderr
A bit of an inelegant fix but given that the error is created only after call to `const_eval_poly()` and that the calling function cannot propagate the error anywhere else, the error has to be explicitly handled inside `mono_item.rs`.
For ref pattern in func param, the mutability suggestion has to apply to the binding. For example: `fn foo(&x: &i32)` -> `fn foo(&(mut x): &i32)` fixes rust-lang#122415
There are many cases where, due to codegen or a massively unruly codebase, a deeply nested call(call(call(call(call(call(call(call(call(f()))))))))) can happen. This is a spot where it would be good to grow our stack, so that we can survive to tell the programmer their code is dubiously written.
…om other hir nodes that were fed
…e a variant of that enum.
Which enables ui tests to use auxiliary binaries. See the added self-test for an example.
…bal_paths, r=petrochenkov Don't trigger `unused_qualifications` on global paths Fixes rust-lang#122374.
…, r=petrochenkov Extend format arg help for simple tuple index access expression The help is only applicable for simple field access `a.b` and (with this PR) simple tuple index access expressions `a.0`. Closes rust-lang#122535.
compiletest: Add support for `//@ aux-bin: foo.rs` Which enables ui tests to use auxiliary binaries. See the added self-test for an example. This is an enabler for the test in rust-lang#121573.
Fix incorrect mutable suggestion information for binding in ref pattern. For ref pattern in func param, the mutability suggestion has to apply to the binding. For example: `fn foo(&x: &i32)` -> `fn foo(&(mut x): &i32)` fixes rust-lang#122415
…manieu Fix ICE: `global_asm!()` Don't Panic When Unable to Evaluate Constant Fixes rust-lang#121099 A bit of an inelegant fix but given that the error is created only after call to `const_eval_poly()` and that the calling function cannot propagate the error anywhere else, the error has to be explicitly handled inside `mono_item.rs`. r? `@Amanieu`
…rgument, r=lcnr Change only_local to a enum type. Change only_local to enum type and change the macros to always require a variant of that enum. r? `@lcnr`
…ll-call-calling-me-maybe, r=compiler-errors Ensure stack before parsing dot-or-call There are many cases where, due to codegen or a massively unruly codebase, a deeply nested `call(call(call(call(call(call(call(call(call(f())))))))))` can happen. This is a spot where it would be good to grow our stack, so that we can survive to tell the programmer their code is dubiously written. Closes rust-lang#122715
…fee1-dead Ensure nested statics have a HIR node to prevent various queries from ICEing fixes rust-lang/miri#3389
[doc]:fix error code example fixs rust-lang#122716
…test, r=compiler-errors add test for casting pointer to union with unsized tail closes rust-lang#122581
@bors r+ rollup=never p=10 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: a385e5667c In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (e760daa): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 667.729s -> 670.459s (0.41%) |
Trying #122435. @rust-timer build 78c3e8d |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (78c3e8d): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDInstruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
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: 667.729s -> 668.055s (0.05%) |
Seems like the improvements outweigh the small regressions. I'm not sure that we need to address this (though don't let that stop anyone from doing so). @rustbot label: +perf-regression-triaged |
Successful merges:
unused_qualifications
on global paths #122435 (Don't triggerunused_qualifications
on global paths)//@ aux-bin: foo.rs
#122634 (compiletest: Add support for//@ aux-bin: foo.rs
)global_asm!()
Don't Panic When Unable to Evaluate Constant #122691 (Fix ICE:global_asm!()
Don't Panic When Unable to Evaluate Constant)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup