[Logging] Mark LogFatal::~LogFatal as [[noreturn]] #13542
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using
LOG(FATAL) << "some error message";throws an exception when the internalLogFatalobject is constructed. However, the gcc warning "control reaches end of non-void function" resulted in a common pattern where aLOG(FATAL)statement was immediately followed by return of a default value, in order to suppress the warning.This commit marks the
LogFatal::~LogFataldestructor with the C++11 attribute[[noreturn]], indicating that calls into it will not resume the normal control flow. This suppresses the warning without requiring the extrareturnstatement afterLOG(FATAL), as the compiler knows that control flow will not resume afterLOG(FATAL).