Re: [PATCH 5/5] midx-write: reenable signed comparison errors
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 28, 2025, 21:01 UTC
- Message-ID
- <xmqqo6rztb2h.fsf@gitster.g>
- In-Reply-To
- <eb1abdca32c64cdabbc92008bf318c7ed67b2c1f.1756402795.git.gitgitgadget@gmail.com>
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> The strategy here involves defining the variable within the for loop > syntax to make sure we use the appropriate bitness for the loop > sentinel. This matters in at least one method where the variable was > compared to uint32_t in some loops and size_t in others.
Sounds like a fine way to avoid accidentally breaking these loops.