-
Notifications
You must be signed in to change notification settings - Fork 4
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
olleH dlroW #1
Comments
Hi :) Sorry, apparently I've spent too much time playing with more recent versions of the dotnet SDK, so I can't build / run this right now. It's been a while, so I don't remember what the expected behaviour is, but at first glance it does look like you're right! I'll try to get it building with a more recent version of the SDK and build a test-harness to try it out. |
(either way, thanks for taking the time to report it!) |
Yep you're right about the order - don't know how I missed that. I'll update the README. That Maybe this is something worth working on over the holiday break :) |
I've closed this issue, but only because I'm tracking the work in #2. Thanks again for the catch. |
I think your Example from the start page produces olleH dlroW and not dlroW olleH. Only the message is reversed (single OnNext argument) and not the whole message list is inverted. Or did I missed something in the code? Cause you didn't add a special threading scheduler for rx pat the order of messages should be delivered as added with OnNext calls. Didn't tried, just reading your code sample... ;-)
The text was updated successfully, but these errors were encountered: