-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
More operators in Rx.Net #634
Comments
Nice list. Catch -> onErrorResumeNext (?) I don't recognize the rest. |
Updated. StartAsync is not the
|
Here is what's missing and what they generally do:
|
@zsxwing or anyone else; do you want to do some of these? I'll do them in batches do I don't have to rebase and restart from master all the time. I'll start with |
Continuing with Update: Wait is practically BO.last(). Since we don't usually do aliases, I'll skip Wait. |
Next: |
I can add SingleAsync and SingleOrDefaultAsync in PR #520 directly. |
Do we really need DeferAsync, ForEachAsync, FromAsync, StartAsync? We have no CancellationToken in Java. |
It appears to me that CancellationToken is used for cancelling tasks, basically a similar way you would use FutureTask and check its isCancelled(), but since these tokens come from the outside, you can signal cancellations to multiple tasks at once. Since we have the |
Doing |
Anyone want to implement all the TestSchedulers? (CancellationToken is really only useful when you have async await). |
A can take those as well, unless someone else beats me to it while I do the ops mentioned above. |
Doing lastasync and lastordefaultasync |
@headinthebox what features do you miss from the current Never mind, I'll start doing it. Btw, I'm starting to require the enhancements of my PRs to avoid feature duplication... |
These are done: Switch -> switchOnNext (?) The "async" ones don't use the async suffix in RxJava since the non-async ones are on |
@zsxwing How is the We have
Difference between |
What is a use case for |
Rx.NET uses it all around the place to hide subjects. @headinthebox might explain it better. |
Interesting, though what value is there in "hiding" it? If it is returned as an |
Yup, as @benjchristensen says, it is to prevent downcasting etc. In .NET people are pretty paranoid about this. Say you have a method that returns an Iterable, but really it is an Array. Now that opens a potential (security) hole since the caller can use the Iterable as a an Array. |
Sorry. Forget it. We just need to add |
Looking into |
SingleAsync has already done in #520 |
Doing ForEachAsync and FromAsync and probably will amend PR #645. |
The |
No, this FromAsync is a completely different operation: it uses a factory to get a future of a value which is then observed; per subscriber. |
Already added the table to the wiki: On Thu, Dec 19, 2013 at 5:57 PM, Shixiong Zhu notifications@github.comwrote:
David M. Gross |
@headinthebox and I reviewed the list. All remaining items have been struck out as they should not be implemented. Great work getting all the others done! |
I extracted the method names from RxJava and Rx.Net and compared them. I find some operators in Rx.Net(version 2.0.20823.0) do not appear in the MSDN. Do we need to implement them before 1.0? Here is the list:
catch(onErrorResumeNext is what we use, this was for F# computation expressions)deferasync(not applicable as we don't haveTask
or async/await)foreachasync(BlockingObservable.forEach since we don't haveTask
or async/await)fromasync(from with Schedulers does this)fromasyncpattern(won't implement)fromevent(won't implement)fromeventpattern(won't implement)getenumerator(won't implement)startasynctoevent(won't implement)toeventpattern(won't implement)wait(BlockingObservable.last())strong means someone is working on it.
strikethroughmeans it won't be implememted.The text was updated successfully, but these errors were encountered: