There is already a popular package called RxDart, so referencing this in your readme makes it look like this is a fork. I would recommend removing all references to RxDart to avoid confusing people who find your package.

RxDart already exists which not only provides the ReactiveX behavior and interfaces in Dart, but does so by extending native Dart streams instead of trying to replace them altogether. (It's also been around a while and has matured and been battle-tested in that time.)

This library's observables not being based on Dart streams seems to be a massive reason to not use this library, and it seems like the only interoperability is a light observable type that wraps the Stream object without exposing it or any of its functionality. and aside from that, there doesn't seem to be any way for a Dart stream to listen to a Dart-Rx observable, which makes working with native stream functions or other third-party library streams incredibly difficult.

So to get to the point, what does this library offer that A) RxDart doesn't already provide, and B) outweighs the loss of nearly all native Stream interoperability?

Just posting this up for discussion. One of the problems with not extending Dart streams is you lose access to features like async generators.

https://www.youtube.com/watch?v=TF-TBsgIErY&t=4m43s

Idiomatic dart doesn't use $ for streams since we have had a strongly typed language from the beginning. While use of $ is common in JavaScript it is very uncommon in Dart. Just a minor nit. I only bring it up because people without rxjs experience will be confused by this use of $

Hi there, really interested in what you're doing here. Just a heads up, consumers of this package will expect to be able to use it with import 'package:rx/rx.dart'. The entrypoint for this package is not clear otherwise.

• First of all, thanks for your nice repo.
• In my case, i need to call the restful app then return the Observable<Result> when complete via emiter like Rxjava into onNext, onError or complete
• The Issuse I meet is I can't make the API call with network without await / async keywork. If the functioin has await keyword, it require async keyword then Future required. But exactly type we need in return is Observable<Result>
  Bellow is my code. I need function getUserObservable return <Observable<UserResponse>> instead Future

In rxjs we can do this:

const test = new ReplaySubject<string>(1);
test.pipe(
	finalize(() => console.log('finalize'))
).subscribe({ next: (n) => console.log(n) });
test.next('test');
test.complete();

Will print:

test
finalize

But using rx:

  var test = ReplaySubject<String>(bufferSize: 1);
  test.finalize(() {
    print('finalized');
  }).subscribe(Observer.next(print));
  test.next('test');
  test.complete();

Will only print:

test

It seems that the new Disposable returned from the subscribe is not being disposed with test.complete() is called.

Greetings, I've been looking at this reactive programming package and really liked the idea of bringing a similar implementation of RxJS / RxJava, I was wondering how I can contribute to this, documentation, adding new operators or something that can help grow this library.

Would be nice to have Observable.pipe instead of having to call .lift every time

I think the answer is no, but I would I like to confirm. Is there any combination of available operators that would result in the same behaviour as the share operator?

If not, I'll send a PR

Do you plan to release a new version soon with the recent fixes and new features?