squiid/rust
1
0
Fork 0
Code Issues Pull requests Projects Activity
rust/compiler/rustc_typeck
History
Esteban Kuber 4951e3ad9e Point at argument when evaluating Path's bounds 
When evaluating an `ExprKind::Call`, we first have to `check_expr` on it's
callee. When this one is a `ExprKind::Path`, we had to evaluate the bounds
introduced for its arguments, but by the time we evaluated them we no
longer had access to the argument spans. Now we special case this so
that we can point at the right place on unsatisfied bounds. This also
allows the E0277 deduplication to kick in correctly, so we now emit
fewer errors.
2021-09-16 12:12:28 +00:00
..
src Point at argument when evaluating Path's bounds 2021-09-16 12:12:28 +00:00
Cargo.toml Warn when [T; N].into_iter() is ambiguous in the new edition. 2021-08-30 21:27:31 +02:00
README.md

README.md

For high-level intro to how type checking works in rustc, see the type checking chapter of the rustc dev guide.