fix: Fix -Werror=nonnull-compare
warning in thread affinity assertion
#10863
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 gcc 12.2.0, passing a
nonnull
argument as parameter to theDEBUG_ASSERT_QOBJECT_THREAD_AFFINITY
macro leads to the followingcompiler warning (or error if the build system was configured with
-DWARNINGS_FATAL=ON
):This can easily be solved by not asserting that the pointer is not
nullptr
. Even if that macro is used with a regular (= notnonnull
pointer), that assetion is unnecessary because the worst that can happen
is a crash (which also makes the developer aware of a problem). When
debug assertions are disabled, the resulting instructions are the same
anyway.