@WG-prioritization/alerts issue #82746 has been requested for prioritization.
tried some manual bisecting , I'm not yet sure where it regresses, but I'm inclined to a
P-high because clippy breaks their CI
is this a clippy ICE? i.e., doesn't it occur with
cargo check or something else?
if so and the cause is in the clippy code, I think this issue should be in the clippy's issue tracker
I'd agree with
P-high, normally it'd be
P-critical for Stable-to-stable.
we usually prioritize Clippy ICE here?
If so, I agree with P-high. But we should still create an issue in the clippy repository
seems it has been fixed already on clippy side: https://github.com/rust-lang/rust-clippy/issues/6539
That’s good. What need to happen to land the fixed clippy version in rustc?
did some investigating with MCVE and turns out it isn't actually a duplicate of it (but it should have a similar cause)
anyway, it's a clippy ICE and I'd transfer the issue to clippy repo
nice investigation work! Yes, please let's move it to the relevant repo (or close it as duplicate if more correct)
(issue was transferred to rust-lang/rust-clippy)