Reduction candidate reshape #4

Open
opened 2026-05-24 22:34:01 +00:00 by mikael-lovqvist · 1 comment

Instead of Rule_Match and Sub_Scan_Rule_Match and such we should have a single record that carries:

  • Rule chain
  • Match slice indices
  • Match object from condition
  • Sequence we match against
Instead of Rule_Match and Sub_Scan_Rule_Match and such we should have a single record that carries: - Rule chain - Match slice indices - Match object from condition - Sequence we match against
Author
Owner

Also note that we should add API to the candidate object to make it easier to build upon, such as a nest(outer_rule) function that builds the rule chain for traceability.

Also note that we should add API to the candidate object to make it easier to build upon, such as a `nest(outer_rule)` function that builds the rule chain for traceability.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: efforting.tech/nodejs.esm-library#4