Esteban Kuber
Esteban Kuber
As implemented, `#![deny(large_assignments)]` relies on a flag being passed to `rustc` or on `#![move_size_limit = N]` being set at the crate level. Would it make sense to instead make `move_size_limit`...
@miam-miam100 it might still be worth it to have a clippy lint against named params *ever* being referred to positionally, which would be noisier/stricter than what this PR and rustc...
Yeah, having that split makes sense to me. Migration is going to be annoying though.
Removing `D-newcomer-roadblock` as the current output is ``` error[E0308]: mismatched types --> src/lib.rs:2:5 | 1 | fn foo() -> i32 { | --- expected `i32` because of return type 2...
This might also be the reason `#` is considered an emoji, which caused a [parsing regression](https://github.com/rust-lang/rust/issues/109746) when trying to recover identifiers with emoji in `rustc`. We're side-stepping the issue by...
Follow @compiler-errors' guidance from [the zulip thread](https://rust-lang.zulipchat.com/#narrow/stream/233931-t-compiler.2Fmajor-changes/topic/uplift.20some.20-Zverbose.20calls.20and.20rename.20to.E2.80.A6.20compiler-team.23706). @rustbot second
Given that this is a user visible flag (otherwise I'd just second): @rfcbot fcp merge
We already have one-off logic in diagnostics to silence redundant errors. We would have to extend those kind of checks to lints as well. Because that kind of silencing requires...