MemoryStream does not multicast properly, repeatedly triggers upstream calls #93
Labels
Comments
|
@xgrommx posted that |
staltz
added a commit
that referenced
this issue
Oct 24, 2016
This fusion puts two consecutive map operators together, disguised as one map operation. This fusion caused undesired issues such as #98, #108, #93. It works in most.js because that one is unicast-first, but map+map fusion does not work well with multicast-only, like in xstream. BREAKING CHANGE: This change will remove map+map fusions. Your application code may or may not rely on the bugs that map+map fusion caused, so we advise to update carefully, testing your application code as you go. Generally this is very straightforward and safe to update, as there are no visible API changes. Closes #98, #108, #93.
|
Fixed in v7.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since it's automatically hot, I expect a
MemoryStreamto allow multicasting without re-triggering the upstream closure chain like a cold stream would, but that's not the behavior I am seeing. Using v5.3.2 the upstream chain seems to be called for each downstream listener: http://www.webpackbin.com/NykQCF-_-When testing with Rx 4 and
shareReplay, I get the behavior I would expect: http://www.webpackbin.com/41l_Yaxu-Isn't
remember()supposed to be equivalent ofshareReplay(1)?The text was updated successfully, but these errors were encountered: