fix(lint): allow defaulted loop counters - #16667
Open
figtracer wants to merge 1 commit into
Open
Conversation
Recognize unsigned for-header counters with upper-bound conditions and increment updates, without suppressing other uninitialized reads or changing loop state restoration.
figtracer
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
mablr,
mattsse and
stevencartavia
as code owners
September 5, 2026 01:40
Contributor
✅ Changelog foundThe deterministic check will validate the changed entry. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recognize the intentional zero start in
for (uint256 i; i < n; ++i)instead of reporting its counter as an uninitialized read. The exception is limited to unsigned counters declared in the header, compared against an upper bound, and incremented with++; declarations outside the header and other uninitialized locals still warn. Loop-body findings and zero-iteration write handling remain unchanged.Fixes #16641.