Why is this an issue?
A catch clause that only rethrows the caught exception has the same effect as omitting the catch altogether and letting
it bubble up automatically, but with more code and the additional detriment of leaving maintainers scratching their heads.
Such clauses should either be eliminated or populated with the appropriate logic.
Noncompliant code example
try {
saveDocument();
} catch (const std::exception& e) { // Noncompliant
throw;
}
Compliant solution
try {
saveDocument();
} catch (const std::exception& e) { // Compliant
log << e.what();
throw;
}
or
saveDocument();
