Remove redundant check for #[loop_match] and #[const_continue]#158138
Conversation
|
Some changes occurred in compiler/rustc_passes/src/check_attr.rs |
|
|
|
Some changes occurred in compiler/rustc_attr_parsing |
#[loop_match]#[loop_match] and #[const_continue]
|
Reminder, once the PR becomes ready for a review, use |
This comment has been minimized.
This comment has been minimized.
remove `check_loop_match` from `check_attr.rs` as it only verifies that the target is a loop, which is already enforced by `check_target` in `target_checking.rs` via `ALLOWED_TARGETS`, and its `LoopMatchAttr` diagnostic.
4ff8f9a to
569a2ff
Compare
remove `check_const_continue` from `check_attr.rs` as it only verifies that the target is a break, which is already enforced by `check_target` in `target_checking.rs` via `ALLOWED_TARGETS`, and it's's `ConstContinueAttr` diagnostic.
569a2ff to
620bf09
Compare
…uwer Rollup of 8 pull requests Successful merges: - #158129 (ensure the new solver bootstraps on CI) - #158134 (Rename `lint-rust-version` to `hint-msrv`) - #157926 (Implement `#[diagnostic::on_unknown]` for modules.) - #158075 (Point to the unstable segment of an import path instead of to the whole path) - #158084 (`-Znext-solver` Emit error instead of ICE when combining {int, float} var with alias) - #158128 (std: use correct low surrogate range in Windows standard I/O code) - #158132 (std: correctly report file size on UWP) - #158138 (Remove redundant check for `#[loop_match]` and `#[const_continue]`)
Rollup merge of #158138 - obeis:move-check-loop-match, r=JonathanBrouwer Remove redundant check for `#[loop_match]` and `#[const_continue]` Updates #153101 remove `check_loop_match` and `check_const_continue` from `check_attr.rs` as they only verifies that the target, which is already enforced by `check_target` in `target_checking.rs` via `ALLOWED_TARGETS`. r? @JonathanBrouwer
|
@rust-timer build cf6f8a0 |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (cf6f8a0): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 2.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -5.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 481.965s -> 482.858s (0.19%) |
Updates #153101
remove
check_loop_matchandcheck_const_continuefromcheck_attr.rsas they only verifies that the target, which is already enforced bycheck_targetintarget_checking.rsviaALLOWED_TARGETS.r? @JonathanBrouwer