Tracking issue: AirScript modularity

[grjte]

Goal(s)

• add modules & imports
• support for functions
• support for evaluators
• support for selectors

Details

These features are described in the original AirScript discussion.

Modules & imports

We want to be able to define functionality in one file and use it in another, e.g.:

use: bar

trace_columns:
  main: [a, b, c, d]
  aux: [e, f]

enf bar(main[0..2], aux[0..1])

Functions

Add function support as described here.

Evaluator functions

Add support for evaluator functions as described here.

Selectors

Add selector support as described here

Tasks

Preview Give feedback

We're having trouble rendering your tasklist, it's most likely has one of the following formatting errors:

• indented tasks (i.e. nested tasklist; support for this is coming!)
• an empty task (i.e. - [ ] on a line by itself)
• any empty new lines (before/after the tasklist or in between tasks)
• duplicate issue/pr links
• a draft task exceeds 512 characters

Please check the tasklists documentation for more information. 🔗 Feedback Discussion

Thank you for participating in the Private Beta ❤️

1. Allow constraints to be written in a modular way #122
   enhancement v0.3 +2
   
2. Add support for functions #123
   enhancement +1
   
3. Add support for evaluator functions #124
   enhancement v0.3 +2
   
4. Add support for selectors #125
   enhancement v0.3 +2
   

Tasks

Preview Give feedback

We're having trouble rendering your tasklist, it's most likely has one of the following formatting errors:

• indented tasks (i.e. nested tasklist; support for this is coming!)
• an empty task (i.e. - [ ] on a line by itself)
• any empty new lines (before/after the tasklist or in between tasks)
• duplicate issue/pr links
• a draft task exceeds 512 characters

Please check the tasklists documentation for more information. 🔗 Feedback Discussion

Thank you for participating in the Private Beta ❤️

No tasks being tracked yet.

Working group:

@torhnii, @grjte, @Overcastan, @Al-Kindi-0

Workflow

• Discussion should happen here or in the related sub-issues.
• PRs should only be merged by the coordinator, to ensure everyone is able to review.
• Aim to complete reviews within 24 hours.
• When a related sub-issue is opened:
  • add it to the list of sub-issues in this tracking issue
• When opening a related PR:
  • request review from everyone in this working group
• When a sub-issue is completed:
  • close the related issue with a comment that links to the PR where the work was completed

Coordinator: @tohrnii

The working group coordinator ensures scope & progress tracking are transparent and accurate. They will:

• Merge approved PRs after all working group members have completed their reviews.
  • add the PR # to the relevant section of the current tracking PR.
  • close any completed sub-issue(s) with a comment that links to the PR where the work was completed
• Monitor workflow items and complete anything that slips through the cracks.
• Monitor scope to see if anything is untracked or unclear. Create missing sub-issues or initiate discussion as required.
• Monitor progress to see if there's anything which isn't moving forward. Initiate discussion as required.
• Identify PRs with especially significant changes and add @grjte and @bobbinth for review.

[grjte]

Superseded by #162