| Age | Commit message (Collapse) | Author | Lines |
|
panic!("a {}", "b") is still not allowed in const,
even if the hir flattens to panic!("a b").
|
|
|
|
Desugaring DropAndReplace at MIR build (#107844) fixed issue
70919. Add regressions tests, borrowed from #102078, to ensure we
check for this in the future.
Co-authored-by: Aaron Hill <aa1ronham@gmail.com>
|
|
This commit desugars the drop and replace deriving from an
assignment at MIR build, avoiding the construction of the
DropAndReplace terminator (which will be removed in a followign PR)
In order to retain the same error messages for replaces a new
DesugaringKind::Replace variant is introduced.
|
|
Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`,
the error message where it gives additional notes about where the associated
type is defined, and how the dead code lint doesn't have an article,
like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have
articles, so it seems unnecessary to have one here.
|
|
|
|
|
|
Provide structured suggestion for binding needing type on E0594
Partially address #45405.
|
|
Partially address #45405.
|
|
Fix #64008.
|
|
Migrate mir_build's borrow conflicts
This also changes the error message slightly, for two reasons:
- I'm not a fan of saying "value borrowed, by `x`, here"
- it simplifies the error implementation significantly.
|
|
|
|
|
|
|
|
CC #99430
|
|
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
|
|
|