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

continuous flows not immediately ready should be considered illegal #50

Closed
leonoel opened this issue Nov 4, 2021 · 1 comment
Closed

continuous flows not immediately ready should be considered illegal #50

leonoel opened this issue Nov 4, 2021 · 1 comment
Labels
breaking change A bad design decision was made

Comments

@leonoel
Copy link
Owner

leonoel commented Nov 4, 2021

Allowing deferred initialization has no obvious benefit and goes against the idea of "defined on every point in time".

This is a requirement for cp #26 , and could simplify implementation of signal!, latest and sample #33 . signal!, latest and sample should fail if input flow is not immediately ready to transfer.
@leonoel leonoel added the breaking change A bad design decision was made label Nov 4, 2021
@leonoel
Copy link
Owner Author

leonoel commented Dec 24, 2021

Fixed in b.25

@leonoel leonoel closed this as completed Dec 24, 2021
@leonoel leonoel mentioned this issue Oct 7, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change A bad design decision was made
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leonoel