Skip to content

timeInterval/timeStamp now operate on the computation, not the immediate, scheduler #278

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
Closed
DavidMGross opened this issue Jul 8, 2016 · 0 comments · Fixed by #424
Closed

timeInterval/timeStamp now operate on the computation, not the immediate, scheduler #278

DavidMGross opened this issue Jul 8, 2016 · 0 comments · Fixed by #424
Labels
RxJava

Comments

@DavidMGross
Copy link
Collaborator

DavidMGross commented Jul 8, 2016 •
edited
Loading

See: ReactiveX/RxJava#4178

The documentation is now incorrect at these three pages:

Also, it's imprecise to say the operators "operate" on that scheduler so much as they use that scheduler to get the time.
@DavidMGross DavidMGross changed the title timeInterval now operates on the computation, not the immediate, scheduler timeInterval/timeStamp now operate on the computation, not the immediate, scheduler Jul 10, 2016
akarnokd added a commit that referenced this issue Jun 5, 2024
@akarnokd
RxJava timeInterval/timestamp runs on computation, resolves #278
3dda5c3
@akarnokd akarnokd mentioned this issue Jun 5, 2024
Merged
akarnokd added a commit that referenced this issue Jun 5, 2024
@akarnokd
RxJava timeInterval/timestamp runs on computation, resolves #278 (#424)
278088e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RxJava
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

RxJava timeInterval/timestamp runs on computation, resolves #278 ReactiveX/reactivex.github.io
1 participant
@DavidMGross