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

Auto-fork Observable operators meant for blocking I/O #777

Closed
alexandru opened this issue Nov 15, 2018 · 0 comments
Closed

Auto-fork Observable operators meant for blocking I/O #777

alexandru opened this issue Nov 15, 2018 · 0 comments
Milestone

Comments

@alexandru
Copy link
Member

Related to: #733

The policy of Monix has been to not auto-fork at the start of a computation, when using Observable.

This is why Observable.fromLinesReader does not fork at the start. However it does eventually fork by default, because it has the batching behavior. But forking at the start of operators that can trigger an blocking I/O operation makes a lot of sense, otherwise it catches users by surprise.

So we need to change builders like Observable.fromLinesReader to do a fork at start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant