Repository navigation
docs(dfns): fix reason for inline-array position rule - #393
Merged
wpbonelli merged 1 commit intoOct 14, 2026
Merged
Conversation
An inline array whose width varies by row (self-sizing, sibling- or lookup-sized) must be a record's last field. The old reason, that a reader couldn't tell where later fields start, is wrong for a sibling, which comes earlier in the row. The reason is that a row's layout should be fixed by the component's dimensions, except for its last field, so a row can be split without evaluating any other field, row or block. A union's arm, and so its width, is chosen by its own tokens, so a union may come anywhere (e.g. utl-obs's id, followed by id2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wpbonelli
added
bug
wpbonelli
changed the title
wpbonelli
marked this pull request as ready for review
October 14, 2026 23:35
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.
An inline array whose width varies by row (self-sizing, sibling- or lookup-sized) must be a record's last field. The old reason, that a reader couldn't tell where later fields start, is wrong for a sibling, which comes earlier in the row. The reason is that a row's layout should be fixed by explicit dimensions, except for its last field.