Introduce vertical void attributes (? > name)#5268
Merged
yegor256 merged 6 commits intoJun 26, 2026
Conversation
Contributor
🚀 Performance AnalysisAll benchmarks are within the acceptable range. No critical degradation detected (threshold is 100%). Please refer to the detailed report for more information. Click to see the detailed report
|
…nes (markdownlint MD031)
Member
Author
|
@yegor256 please have a look |
|
|
@maxonfjvipon Thanks for the contribution! You've earned +4 points for this: +16 as a basis; -4 for too many hits-of-code (486 >= 100); -8 for way too many hits-of-code (486 >= 400). Please, keep them coming. Your running score is +394; don't forget to check your Zerocracy account too). |
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
3 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.
Implements the
?-headed body-line forms from the fragile-objects epic #5261.Part 1 — vertical void attributes. A
? > namebody line declares a void attribute, equivalent to listingnamein the bracket params, emitting the same<o name="name" base="∅"/>;move-voids-uphoists it — no XSL/runtime/transpiler change.?is a dedicated line shape (LnVoid), never a value — so?.read,foo ? bar,foo. ? q, bare?, and a void with children are all rejected.Part 2 — atom error-formas. In an atom, a void may carry
? > not-found /{string io.file-error}, emitting a@typesattribute whose tokens resolve exactly like@atom(leadingQ.→Φ.at parse; then alias-expanded andΦ.-prefixed when dotless), e.g.types="Φ.string io.file-error". Rejected outside an atom. Resolution reuses the pipeline via an attribute-levelmatch="@types"template inresolve-aliases.xslandadd-default-package.xsl.PARSER_SPEC.mdR-3.4.7/R-3.4.8 and parse/EoTestpacks cover both parts. Green with-Pqulice.Closes #5267.