-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
ReplaySubject Time and Capacity #865
Comments
Hi guys, I'll begin working on this. |
Does it need to solve issue #658 as well? |
Yes it does, thanks for reminding me of that one. |
This item is open to be worked on as @katzseth22202 has been pulled away to something else. |
This is being done as part of #1211 |
Merged in #1223 |
jihoonson
pushed a commit
to jihoonson/RxJava
that referenced
this issue
Mar 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The various
replay
overloads ended up getting implemented in a privateSubject
implementation insideOperationReplay
(https://github.com/Netflix/RxJava/blob/master/rxjava-core/src/main/java/rx/operators/OperationReplay.java?source=c#L699). This functionality needs to live onReplaySubject
itself.This was brought up with some of the functionality added in: #753
Issues related to this are:
The text was updated successfully, but these errors were encountered: