Rather than using plain generic verifyNotNull(), provide some context
to improve diagnostics when verification actually fails.
Change-Id: I211f7c81cf7d369af521953cd747bed06a89c360
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
@Override
public Collection<? extends StatementContextBase<?, ?, ?>> mutableDeclaredSubstatements() {
- return verifyNotNull(substatements);
+ return verifyNotNull(substatements, "Substatements no longer available in %s", this);
}
@Override
}
final OriginalStmtCtx<?, ?, ?> getResumedSubstatement() {
- final var local = verifyNotNull(effective);
+ final var local = verifyNotNull(effective, "Effective substatements no longer available in %s", this);
verify(!local.isEmpty(), "Unexpected empty statements");
final var ret = local.get(0);
verify(ret instanceof OriginalStmtCtx, "Unexpected statement %s", ret);
}
private StatementSupportBundle.@NonNull Builder getBuilder(final ModelProcessingPhase phase) {
- return verifyNotNull(reactorSupportBundles.get(phase));
+ return verifyNotNull(reactorSupportBundles.get(phase), "No builder for %s found", phase);
}
}