docs: clarify loop invariants with break and goto - #9136
Closed
tomatotomata wants to merge 1 commit into
Closed
Conversation
Explain the non-strict treatment of loop exits and keep the transformed example valid C by replacing its illustrative break with a goto.
tomatotomata
requested review from
feliperodri,
kroening,
peterschrammel,
remi-delmas-3000 and
tautschnig
as code owners
July 28, 2026 16:28
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
1 participant
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.
Summary\n\n- replace the illustrative �reak in the transformed loop-invariant example with a valid goto exit\n- document the non-strict treatment of �reak and loop-exiting goto paths\n\nFixes #8812\n\n## Validation\n\n- git diff --check\n\nThis is a documentation-only change.