Came across this blogpost about the cool clang error recovery features:
Clang really goes "above and beyond the call of duty" to deliver good error messages. For example, it has a built-in spell-checker, so that if you type "int64" instead of "int64_t", it will actually point that out. It also detects source code conflict markers, and only parse one side of it (failing of course, but without attempting to parse the conflict markers).
This is probably very true: