RepeatOrNot about repeater HOT 1 OPEN

Sorry for the sluggish response! I hear what you’re saying! I also sometimes wonder about writing simultaneously thenable/async iterable APIs. However, I’m not really sure baking this pattern into the repeater abstraction is the right way to go about things. My guess is, you could probably write your RepeaterOrNot API in user space by composing the repeaters with your own code.

I’m on my phone now, so I’m not really able to write the code that would make this work, but essentially you would create a class which mirrors the Repeater class, construct and retain a repeater instance in the constructor, pass in the modified push and stop functions according to your specification and then implement the then/catch/finally/next/return/throw methods according to your specifications as well?

While I don’t think your proposed API is going to make it in, I encourage to experiment via composition, and if you have any questions or need help, I encourage you to let me know via this issue or by email!

from repeater.