You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: