Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acrions, triggers, and queries #14

Open
VonTum opened this issue Oct 20, 2024 · 0 comments
Open

Acrions, triggers, and queries #14

VonTum opened this issue Oct 20, 2024 · 0 comments
Labels
enhancement New feature or request Request Input These are issues about the design of the language, and thus should be discussed

Comments

@VonTum
Copy link
Collaborator

VonTum commented Oct 20, 2024

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.

image

@VonTum VonTum added enhancement New feature or request Request Input These are issues about the design of the language, and thus should be discussed labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Request Input These are issues about the design of the language, and thus should be discussed
Projects
None yet
Development

No branches or pull requests

1 participant