Skip to content

Model element-context array values (Sorted/Filtered Array, Is True For All/Any, Current Array Element/Index) #60

Description

@e54-bot

Problem

Follow-up to athena#56. The first PR modeled the element-free general and array values; these remain because they evaluate their operand once per element with 'Current Array Element' (and 'Current Array Index') bound.

Scope

'Current Array Element', 'Current Array Index', 'Sorted Array', 'Filtered Array', 'Is True For All', 'Is True For Any', 'Mapped Array' if Bastion's run reaches it, plus 'Evaluate Once' and 'Local Player' if they prove to be the blocker ahead. Semantics follow 'workshop-rs' definitions; array and null coercions follow 'docs/architecture.md'.

Acceptance criteria

  • One unit test per value family with a boundary case (empty array, null operand, out-of-range index).
  • Standard gates: fmt, clippy -D warnings, tests, wasm32 build; update 'docs/simulator-interface.md' in the same PR. A construct without a passing capture fixture is recorded in 'docs/findings.md' as modeled-not-measured.
  • The Bastion run moves past 'value evaluateOnce' at tick 0 (the stop athena#56's first PR left); record the next stop in the PR body.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestp1Critical path of the current roadmap line, or a bug that hits real workflowsready-for-implementationContract settled; an Engineer can implement without inventing a decision

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions