Codechange: "set but not used" warning when disabling assert() #9613
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.
Motivation / Problem
During preparing for 12.0, the PR that disables
assert()
notice one new warning. Let's make a clean release, and address that warning.Description
DebugCheckSanity()
is unused when asserts are disabled.Owh, and we should be using
WITH_ASSERT
, notNDEBUG
for these cases.Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.