I'd much rather have a helpful compiler error than run something that has been "repaired" and may silently do the wrong thing.
This is what compilers do already, one such strategy is to unwind the state to before the error and skip over the erroneous part. This can be a bit problematic in certain situations, such as a syntax error in a variable definition and the following flood of 'undefined variable' errors.
The repair strategy in the article is trying to optimise the quality of the attempted repair in order to provide better error messages to the user.