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

Document Stream Spec vs Observable Spec quirks #71

Closed
3 tasks done
brianegan opened this issue Feb 24, 2017 · 1 comment · Fixed by #78
Closed
3 tasks done

Document Stream Spec vs Observable Spec quirks #71

brianegan opened this issue Feb 24, 2017 · 1 comment · Fixed by #78
Milestone

Comments

@brianegan
Copy link
Collaborator

brianegan commented Feb 24, 2017

This includes:

  • Dart Sync vs Async Streams vs / in combination with Rx Schedulers as we introduce that concept
  • Return type of first, last, etc returns Future not an Observable
  • Error contract in Observable (closes stream) vs Dart (does not by default)
@lestathc
Copy link

Suggestion, may want to mention:
StreamController onListen side effect triggering logic is different than Observable onSubscribe (for create operator).

Well, Observable onSubscribe is not officially documented in ReactiveX that it must be called every time Observable is subscribed, but it is in all existing rx implementations.

But for broadcast stream, the onListen is only be called at the first time it is subscribed, so that it is equal to observable.publish().autoConnect(1). (For non-broadcast stream, it is fine since it can not be subscribed multiple times)

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

Successfully merging a pull request may close this issue.

2 participants