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

Implement some way to express that a signal doesn't need to be evaluated #23

Open
colinbdclark opened this issue Feb 8, 2022 · 0 comments

Comments

@colinbdclark
Copy link
Contributor

Currently, we have a "Value" signal that simply outputs a buffer containing a static value, though it can be updated arbitrarily by the user. However, there's no way to express that the value is constant throughout the lifetime of the program. As a result, we pay some cost in having to continually evaluate all signals at runtime.

This might be as simple as introducing a ConstantValue signal, but it would be nice for this to be a qualifier for any type of signal.

This may or may not dovetail with performance optimizations that could be implemented to only evaluate signals such as Value (which may only be updated rarely) when necessary.

colinbdclark added a commit to colinbdclark/signaletic that referenced this issue Oct 14, 2022
Also includes initial infrastructure for improved input creation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant