cache: Weird behaviour on throw

[ValentinFunk]

RxJS version: 5.0.0-beta.12

Code to reproduce:

const throwsInstantly = Rx.Observable.throw("E");

throwsInstantly.cache(1).subscribe(
  x => console.log(x),
  error => console.error("Cache", error),
  () => console.log("Done")
);

Example: https://codepen.io/Kamshak-1472390889/pen/gwowkZ?editors=0010#0

Expected behavior: Console prints "Cache E": The error is passed on.

Actual behavior: No output.

Additional information: Is this expected? The behaviour is different if the observable throws after the cache is subscribed (error is passed on).

[benlesh]

I think this is a clincher for removing cache until we can further refine the desired behaviors.

[Dorus]

This fails for Rx.Observable.throw("E", Rx.Scheduler.queue); but works correct under Rx.Scheduler.asap, Rx.Scheduler.async, Rx.Scheduler.animationFrame and new Rx.TestScheduler().

Also this bug has been introduced between [email protected] and [email protected].

[jayphelps]

@Dorus we ended up removing the .cache() operator for RC1 because in it's current state it was too confusing and [poorly] trying to solve too many problems.

We do plan to revisit in the future and possibly provide one or more operators that have differing forms of caching.

Everyone has differing opinions and use cases for what "caching" should mean and it's far more complex that it may seem at first. Some additional thoughts can be found here.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.