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

Operator window with boundary (exact, selector, exact + supplier). #3262

Merged
merged 1 commit into from
Sep 1, 2015

Conversation

akarnokd
Copy link
Member

@akarnokd akarnokd commented Sep 1, 2015

I'm not 100% certain about the state management: when to let the main
source keep running and when to stop. I.e., the in the selector version,
if the other completes, it means no new window will be opened but the
active should keep receiving values until their closer fires. If all
such closers have fired, the main can be stopped.

I'm not 100% certain about the state management: when to let the main
source keep running and when to stop. I.e., the in the selector version,
if the other completes, it means no new window will be opened but the
active should keep receiving values until their closer fires. If all
such closers have fired, the main can be stopped.
@akarnokd akarnokd added this to the 2.0 milestone Sep 1, 2015
akarnokd added a commit that referenced this pull request Sep 1, 2015
Operator window with boundary (exact, selector, exact + supplier).
@akarnokd akarnokd merged commit bfd4bd0 into ReactiveX:2.x Sep 1, 2015
@akarnokd akarnokd deleted the WindowBoundary2x branch September 1, 2015 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant