Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | When typo-correcting a function name, consider correcting to a type name | Richard Smith | 2019-05-09 | 1 | -0/+7 |
| | | | | | | for a function-style cast. llvm-svn: 360302 | ||||
* | Wire up delayed typo correction to DiagnoseEmptyLookup and set up | Kaelyn Takata | 2014-11-20 | 1 | -3/+1 |
| | | | | | | | | | Sema::ActOnIdExpression to use the new functionality. Among other things, this allows recovery in several cases where it wasn't possible before (e.g. correcting a mistyped static_cast<>). llvm-svn: 222464 | ||||
* | When we run into an error parsing or type-checking the left-hand side | Douglas Gregor | 2010-09-17 | 1 | -1/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | of a binary expression, continue on and parse the right-hand side of the binary expression anyway, but don't call the semantic actions to type-check. Previously, we would see the error and then, effectively, skip tokens until the end of the statement. The result should be more useful recovery, both in the normal case (we'll actually see errors beyond the first one in a statement), but it also helps code completion do a much better job, because we do "real" code completion on the right-hand side of an invalid binary expression rather than completing with the recovery completion. For example, given x = p->y if there is no variable named "x", we can still complete after the p-> as a member expression. Along the recovery path, we would have completed after the "->" as if we were in an expression context, which is mostly useless. llvm-svn: 114225 | ||||
* | Teach typo correction about various language keywords. We can't | Douglas Gregor | 2010-04-14 | 1 | -0/+11 |
generally recover from typos in keywords (since we would effectively have to mangle the token stream). However, there are still benefits to typo-correcting with keywords: - We don't make stupid suggestions when the user typed something that is similar to a keyword. - We can suggest the keyword in a diagnostic (did you mean "static_cast"?), even if we can't recover and therefore don't have a fix-it. llvm-svn: 101274 |