Skip to content

Add runtime-sized sequence action composition - #84

Merged
mtc1122 merged 23 commits into
mainfrom
pressure/runtime-sequence-consumption
Nov 17, 2026
Merged

mtc1122 merged 23 commits into
mainfrom
pressure/runtime-sequence-consumption

Conversation

@mtc1122

@mtc1122 mtc1122 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Closes the runtime-length route composition pressure without adding a general loop or collection API.

  • accepts primitive-element ordinary sequence values such as [Int] as immutable action input
  • carries ordinary runtime-sized sequences through both plain and partial-persistent host value boundaries
  • keeps ordinary value sequences distinct from modeled-identity [live T] carriers
  • infers ordered repeated nested action application when exactly one ordinary [T] argument supplies a scalar T value parameter
  • evaluates the sequence and scalar companion values once at the call site
  • reuses scalar companions for each repeated application
  • preserves the existing shared action transaction, including transaction-visible prior steps and whole-route rollback
  • records the checker-selected lifted argument structurally so runtime does not rediscover it from evaluated values

Semantic boundary

The selected rule is deliberately narrow.

  • multiple sequence-to-scalar argument mismatches remain rejected rather than guessing zip, Cartesian-product, broadcast, or nested traversal semantics
  • lifted calls cannot contain writable state parameters; value traversal does not infer writable authority
  • [live T] modeled-identity sequences remain outside ordinary host/action value input
  • no general each, loop, iterator, cursor, map, stable route-element identity, action returns, or collection API is added
  • ordinary non-lifted action calls retain their existing source-shaped runtime path

Pressure evidence

The route pressure establishes:

  • repeated top-level host calls cannot provide whole-route atomicity
  • bounded nested source actions already provide ordering, staged visibility, and rollback
  • runtime-sized [Int] input can cross the host boundary as structured data
  • one sequence mismatch has a mechanically inferable traversal shape
  • two sequence mismatches are semantically ambiguous
  • scalar companion values are captured once and reused
  • empty input performs zero repeated applications
  • writable authority remains a separate explicit semantic axis

Documentation

Updates:

  • docs/LANGUAGE_REFERENCE.md
  • docs/DESIGN_DECISIONS.md
  • CHANGELOG.md

Validation

Targeted local pressure tests were green before the final checked-program metadata refinement.

Exact-head GitHub CI is green at 4e36512d5e5e21b9e8ab87b5fb896f3ddc85330c:

  • cargo fmt --check
  • cargo clippy -- -D warnings
  • cargo test
  • cargo build
  • python -m pytest -v

Full required Windows local validation also passed on the exact same head:

  • cargo fmt
  • cargo fmt --check
  • cargo clippy -- -D warnings
  • cargo test
  • cargo build
  • py -m pytest -v

GitHub CI and local validation therefore agree on 4e36512d5e5e21b9e8ab87b5fb896f3ddc85330c.

@mtc1122
mtc1122 marked this pull request as ready for review November 17, 2026 21:00
@mtc1122
mtc1122 merged commit 6378be0 into main Nov 17, 2026
2 checks passed
@mtc1122
mtc1122 deleted the pressure/runtime-sequence-consumption branch November 17, 2026 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant