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.

Sign up for GitHub

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

Jump to bottom

Enforce conjunction signal temporal order #160

Open
josephbirkner opened this issue Oct 18, 2020 · 0 comments
Open

Enforce conjunction signal temporal order #160

josephbirkner opened this issue Oct 18, 2020 · 0 comments
Assignees
@josephbirkner
Labels
core ⚙️ Issues that concern the core ravestate lib/API

Comments

@josephbirkner
Copy link
Collaborator

Currently, signal conjunctions like a & b do not have any temporal implication for the order in which the signals must arrive. This is a performance bottleneck - many specific states should only be considered if they have already acquired their specific signal(s), and not block processing of a more generic signal otherwise.
@josephbirkner josephbirkner added the core ⚙️ Issues that concern the core ravestate lib/API label Oct 18, 2020
@josephbirkner josephbirkner self-assigned this Oct 18, 2020
@josephbirkner josephbirkner changed the title Enforce ordered conjunction signal order Enforce conjunction signal temporal order Oct 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@josephbirkner josephbirkner

Labels
core ⚙️ Issues that concern the core ravestate lib/API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@josephbirkner