Change "Bad computed nullability" message to be more specific.
When I encountered this message, it wasn't clear to me what was bad about
the nullability. The new message makes it clear that the number of entries in
the vector is wrong.
PiperOrigin-RevId: 522311105
diff --git a/nullability_verification/pointer_nullability_analysis.cc b/nullability_verification/pointer_nullability_analysis.cc
index a8a1a16..2d095a5 100644
--- a/nullability_verification/pointer_nullability_analysis.cc
+++ b/nullability_verification/pointer_nullability_analysis.cc
@@ -55,7 +55,8 @@
ExpectedSize != Nullability.size()) {
// A nullability vector must have one entry per pointer in the type.
// If this is violated, we probably failed to handle some AST node.
- llvm::dbgs() << "=== Bad computed nullability: ===\n";
+ llvm::dbgs()
+ << "=== Nullability vector has wrong number of entries: ===\n";
llvm::dbgs() << "Expression: \n";
dump(E, llvm::dbgs());
llvm::dbgs() << "\nNullability (" << Nullability.size()
