about summary refs log tree commit diff
path: root/src/test/ui/parse-error-correct.stderr
AgeCommit message (Collapse)AuthorLines
2020-12-31Move parser-related testsYuki Okushi-33/+0
2020-01-08Remove `-Z continue-parse-after-error`Vadim Petrochenkov-4/+4
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-1/+1
2019-03-11Update testsVadim Petrochenkov-5/+5
2018-12-25Remove licensesMark Rousskov-4/+4
2018-11-10in which the E0618 "expected function" diagnostic gets a makeoverZack M. Davis-1/+3
Now the main span focuses on the erroneous not-a-function callee, while showing the entire call expression is relegated to a secondary span. In the case where the erroneous callee is itself a call, we point out the definition, and, if the call expression spans multiple lines, tentatively suggest a semicolon (because we suspect that the "outer" call is actually supposed to be a tuple). The new `bug!` assertion is, in fact, safe (`confirm_builtin_call` is only called by `check_call`, which is only called with a first arg of kind `ExprKind::Call` in `check_expr_kind`). Resolves #51055.
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+31