-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 4 pull requests #131988
Rollup of 4 pull requests #131988
Conversation
I found builder.rs to be a massive file which made it hard to digest. To make `RUSTFLAGS` usage hardening easier later, I extracted the cargo part in `builder.rs` into its own module.
…chenkov Added more scenarios where comma to be removed in the function arg This is an attempt to address the problem methion in rust-lang#106304 (comment). Copy the annotation to explain the fix If the next Error::Extra ("next") doesn't next to current ("current") ``` fn foo(_: (), _: u32) {} - foo("current", (), 1u32, "next") + foo((), 1u32) ``` If the previous error is not a `Error::Extra`, then do not trim the next comma ``` - foo((), "current", 42u32, "next") + foo((), 42u32) ``` Frankly, this is a fix from a test case and may not cover all scenarios
bootstrap: extract builder cargo to its own module I was looking at our cargo rustflags/rustdocflags usages, and I found `builder.rs` to be a large file which made it hard to digest. This PR tries to break out the cargo command wrapper parts to its own submodule to make it easier to identify builder cargo-specific logic. This PR: - Extracts the cargo command wrapper to its own module and also move `Builder::{bare_,}cargo` impl to the submodule. - Reorganizes some imports in `lib.rs` (no functional changes). - Slightly adjusts some docs in `builder.rs`. This PR is basically just moving code around, and should not contain any functional changes. Before this PR, `builder.rs` was 2743 lines. After this PR, `builder.rs` is down to a more manageable 1386 lines and `cargo.rs` is 1085 lines.
…g, r=fee1-dead Rip out old effects var handling code from traits Traits no longer have an effect parameter, so this removes logic associated with it. It also removes logic surrounding confirming `~const Destruct` bounds, which I added a looooong time ago, and which I don't feel like we need anymore -- if it needs to be added back, it should be rewritten :D cc `@fee1-dead`
…=cjgillot Remove the `BoundConstness::NotConst` variant I find it easier to represent `BoundConstness::NotConst` as just `None` for some refactorings I'm doing.
@bors r+ rollup=never p=4 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: f2ba41113d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (93742bd): 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.1%, secondary -3.7%)This 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: 781.789s -> 780.893s (-0.11%) |
…iaskrgr Rollup of 4 pull requests Successful merges: - rust-lang#126588 (Added more scenarios where comma to be removed in the function arg) - rust-lang#131728 (bootstrap: extract builder cargo to its own module) - rust-lang#131968 (Rip out old effects var handling code from traits) - rust-lang#131981 (Remove the `BoundConstness::NotConst` variant) r? `@ghost` `@rustbot` modify labels: rollup
Successful merges:
BoundConstness::NotConst
variant #131981 (Remove theBoundConstness::NotConst
variant)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup