flattenSequentially: fix behaviour of outer stream completion (fd31d49), closes #141
BREAKING CHANGES
flattenSequentially: If your code was relying on buggy behavior, you may need to migrate carefully. Check your usages of
flattenSequentially and how the outer stream completes.
MemoryStream: fix a leaking execution bug (47e67ff), closes #53
BREAKING CHANGES
map: 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.
MemoryStream: This is generally safe to update, but note that the behavior around
MemoryStream, startWith, take, imitate etc may have slightly changed, so
it is recommended to run tests on your application and see if it is
working, in case your application code was relying on buggy behavior.