-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 7 pull requests #116054
Rollup of 7 pull requests #116054
Conversation
We only want the attribute for the attribute revision.
To make failing tests easier to debug with --emit=mir, etc.
… r=m-ou-se Command: also print removed env vars There is no real shell syntax for unsetting an env var so easily, so we have to make one up. But we already do that for showing the 'program' name so I hope that's okay here, too. No strong opinion on what that should look like, I went with `unset(VAR_NAME)` for now.
…tcase, r=estebank add UI test for delimiter errors Fixes rust-lang#98601 from rust-lang#98601 (comment) r? `@estebank`
tests/ui: Split large_moves.rs and move to lint/large_assignments To make failing tests easier to debug with `--emit=mir`, etc. Don't bother with `revisions: attribute option` for both tests though. Seems sufficient to just have that on one of the tests. `git show -M --find-renames=40%` makes the diff easier to review. Or note that before this change we had one test with 4 errors, now we have 2 tests with 2 errors each. r? `@oli-obk` Part of rust-lang#83518
…-bug, r=cuviper Fall back to _SC_NPROCESSORS_ONLN if sched_getaffinity returns an empty mask Followup to rust-lang#115946 A gentler fix for rust-lang#115868, one that doesn't panic, [suggested on zulip](https://rust-lang.zulipchat.com/#narrow/stream/259402-t-libs.2Fmeetings/topic/Meeting.202023-09-19/near/391942927) In that situation - on the buggy kernel versions - a zero-mask means no affinities have been set so `_SC_NPROCESSORS_ONLN` provides the right value.
…rrors Account for nested `impl Trait` in TAIT Fix rust-lang#116031. r? `@compiler-errors`
…Jung Add note to `is_known_rigid` Adds a note requested by `@RalfJung` in rust-lang#114941 (comment) Let me know if there are any other fns that need documentation, I could throw them into this PR too :)
give FutureIncompatibilityReason variants more explicit names Also make the `reason` field mandatory when declaring a lint, to make sure this is a deliberate decision.
@bors r+ rollup=never p=7 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 5a4e47ebed In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (03c199a): 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)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: 633.83s -> 634.55s (0.11%) |
Successful merges:
impl Trait
in TAIT #116039 (Account for nestedimpl Trait
in TAIT)is_known_rigid
#116041 (Add note tois_known_rigid
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup