refactor: fix unread variable warnings #4405
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.
Description of changes:
Cppcheck is failing in #4404 because zero initializing variables is causing new
unreadVariable
warnings to surface. Rather than adding new suppressions, this PR fixes those warnings by pushing the variable declaration down a scope.This is being done in a separate PR to keep #4404 as an entirely automated PR.
Call-outs:
Note that under any reasonable optimization level this code is expected to be identical. This was spot checked with GodBolt: https://godbolt.org/z/vaYeWecfM.
Testing:
I first gathered all of the unreadVariable warnings from cppcheck. After fixing those, I first reapplied the clang-tidy fixes
I then ran cppcheck
I finally verified that there were 0 unreadVariable warnings in the new report.
Current CI and tests should be sufficient to ensure that there was no behavior change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.