Error out on invalid input.
In this CL we make sure that:
* we do not visit AST if it has errors
* we return nonzero exit code if the input headers had errors
* we delete output files if the input headers had errors (this is the behavior of Clang as well)
We do not need to be able to process partially incorrect headers, we assume all input it valid C++. In case of errors Clang will print errors to stderr, so the user will be informed about the cause of the failure.
PiperOrigin-RevId: 391482623
diff --git a/rs_bindings_from_cc/ast_consumer.cc b/rs_bindings_from_cc/ast_consumer.cc
index 9fc3c1b..d383004 100644
--- a/rs_bindings_from_cc/ast_consumer.cc
+++ b/rs_bindings_from_cc/ast_consumer.cc
@@ -11,6 +11,13 @@
namespace rs_bindings_from_cc {
void AstConsumer::HandleTranslationUnit(clang::ASTContext &ast_context) {
+ if (ast_context.getDiagnostics().hasErrorOccurred()) {
+ // We do not need to process partially incorrect headers, we assume all
+ // input is valid C++. If there is an error Clang already printed it to
+ // stderr; the user will be informed about the cause of the failure.
+ // There is nothing more for us to do here.
+ return;
+ }
ast_visitor_.TraverseDecl(ast_context.getTranslationUnitDecl());
}
