Repository navigation
Conversation
Ports #1014 alone onto #1015's maps, without #1012 or #1013. A dimension takes `over:` and `missing:`; each member is an implied map of the dimension, read as `connection[unit]`, beside the maps the file declares under `maps: connection:`. A declared map named after a member is refused. A bound over a member suggests a constraint through `at`, since a bound does not read through a map here. Co-Authored-By: Fabian Hofmann <fab.hof@gmx.de> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Documentation build overview
49 files changed ·
|
This was referenced Nov 16, 2026
With the alias underneath, a dimension's members are a list of
dimensions, each once. The role form (`over: {from: region, to:
region}`) is gone: a tuple that holds one dimension twice lists an alias
of it as a member, and `over: [region, region]` is refused with the alias
as the rewrite. The two branches that only roles reached are removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
…maps-tuple-dimensions
The TIMES trade example in this PR's spelling: top_ire is a dimension over the two aliases and the two plain dimensions, and ire_flo, trade_cost and export are over it. capacity.yaml keeps its relations: rtp_vintyr has an ordered member, which a tuple dimension cannot step along. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
…maps-tuple-dimensions
sparse.yaml in this PR's spelling: connection is a dimension over unit and port, capacity is read through at(), the sum per unit groups by the member, and active stays a relation because ramp_up steps along its ordered member. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Contributor
Author
|
Note The following content was generated by AI.
Generated by Claude Code |
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.
Note
The following content was generated by AI.
What this changes
Option C of three for a sparse set: a dimension lists its members under
over:, its label is the tuple, and every operator treats it as one opaque dimension. #1014 alone, ported onto maps, and stacked on #1020 (alias) in place of #1014's role form.The TIMES examples (
examples/times/)capacity.yamlis unchanged:rtp_vintyrhas the ordered memberperiod, which a tuple dimension cannot step along, so it stays a relation withwhere:over: [region, region]is refused: "Declare an alias of 'region' under dimensions:, such as from_region: {alias: region}, and list it in place of one 'region'."Why
connection_busrelation becomes maps ofconnection: one name fewerMethod, gate output, where the port departs from #1014
git diff origin/feat/bound-at origin/feat/tuple-dimensions(feat(language): a dimension lists its members #1014 only, not fix(language): cases read through one relation load #1012 or feat(language): a bound reads a member's parameter #1013), squashed onto feat(language)!: maps give labels, relations give rows #1015; co-authored by @FabianHofmann; then feat(language): a dimension may alias another's labels #1020 merged in (029f548,ce4c86e)over:takes a list only; the "role named after another dimension" refusal and the two branches only roles reached (_dimensions._sum_through,_member_columns) are gone; tests rewritten to an alias member; goldencorridorisover: [from_bus, bus]missing: refused), built insubject_tables;Relation.membersnames them (new program field). A declared map named after a member is refusedover=a member,within=at()in bounds): the bound-through-attest dropped; a bound over a member suggests a constraint instead; goldensite_outuseswhere:in place of theat()bound;bus_outgone fromtools/notation.pytop_ireprints aslover\mathcal{L}(symbol table)ce4c86e: ruff, ruff format, pyrefly (0 errors), pytest (4303 passed, 1 skipped), typos,zensical build --strict, prettier on changed files; every generator run. Not run:compile-tex; no pixi, uv venv🤖 Generated with Claude Code
https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q