Stop causing errors when consuming unbounded sequences #161
Description
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.