C-238 evidence: bound-range list concatenation materializes on every leg - #27
Open
O6lvl4 wants to merge 1 commit into
Open
C-238 evidence: bound-range list concatenation materializes on every leg#27O6lvl4 wants to merge 1 commit into
O6lvl4 wants to merge 1 commit into
Conversation
…leg (greenfield fuzz catch 4)
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
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.
Greenfield fuzz catch #4 (2026-08-21, differential seeds 47/83/89, new range-bind generator arm):
[1, 2] + rwhereris a let-bound range.[1, 2, 0, 1]).internal: list concat— fixed in greenfield 9e6049d65 (ConcatList now takes List|Range through as_iter_items; over-cap spans abstain like index/len, C-197 territory).01[1, 2, 0, 1][3, 4, 5, 7][1, 2]exit 0. contracts.toml evidence row added under C-238; conformance.md and README regenerated; check-contracts.sh and check-als-style.sh green (593/593 fixtures linked).Greenfield will claim the row at the next als pin bump (2-PR flow).
🤖 Generated with Claude Code