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

Stop causing errors when consuming unbounded sequences #161

Open
pineapplemachine opened this issue Oct 6, 2017 · 0 comments
Open

Stop causing errors when consuming unbounded sequences #161

pineapplemachine opened this issue Oct 6, 2017 · 0 comments
Labels
effort: moderate The issue will probably take a single contributor one or two days of work to resolve. meta: next release The issue must be resolved before the next version can be released. priority: high The issue substantially impedes people's ability to use the software. type: polish The issue involves making existing functionality more usable.

Comments

@pineapplemachine
Copy link
Owner

Currently, in most places, passing an unbounded sequence or not-known-bounded sequence to a function that would attempt to consume it entirely will cause an error. There are some situations where the user is absolutely required to use an .assumeBounded() call to make a chain evaluate, and that is not intuitive or user-friendly.

Additionally, there are some cases where a user may want to produce an infinite loop across an unbounded sequence, for example as an asynchronous background task or a synchronous main loop.
@pineapplemachine pineapplemachine added effort: moderate The issue will probably take a single contributor one or two days of work to resolve. priority: high The issue substantially impedes people's ability to use the software. type: polish The issue involves making existing functionality more usable. meta: next release The issue must be resolved before the next version can be released. labels Oct 6, 2017
pineapplemachine added a commit that referenced this issue Nov 20, 2017
@pineapplemachine
Reverse function now accepts unidrectional unknown-bounds inputs
8fcc3c8 
Previously it would always cause an arguments error

Related to #161
@pineapplemachine pineapplemachine mentioned this issue Nov 20, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: moderate The issue will probably take a single contributor one or two days of work to resolve. meta: next release The issue must be resolved before the next version can be released. priority: high The issue substantially impedes people's ability to use the software. type: polish The issue involves making existing functionality more usable.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pineapplemachine