Actions, triggers, and queries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This ties together with Conditional Bindings
Basically, actions, triggers and queries form a natural way to "act" or "respond to" events that submodules create. The natural implementation is adding an extra "invisible" condition wire, that is "1" when the action needs to be triggered (and thereby the associated data is valid).
Actions are triggered by the parent module. They tell the submodule to do something
Triggers are signals sent by a submodule. They tell the parent module to do something
Queries are initiated by the parent module, they're basically an action, that is fallible. So the response from the submodule is conditional.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with philosophy/control_flow.md, especially the Conditional Bindings section, and review the issue's definitions and diagram for actions, triggers, and queries. Before implementation, establish the affected compiler entry points and acceptance tests; done should demonstrate the described parent-to-submodule actions, submodule-to-parent triggers, and conditional query responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100