Dante

The only suspect feeling I have is this is strictly using an external library wrapping a combine -- I understand wanting to present modules that provide functionality like Kefir or...

@paldepind, I was actually thinking of how to nicely represent end streams (I've been tinkering with a stream representation inspired by flyd -- trying to figure out what the concerns...

Yes, wrapping functions in an attempt also works. I can 100% solve this on my end, and have -- but I am throwing into question a way to either inspect...

Sure, I'll reference that issue and close this one out -- that or we can revive discussion on it somewhere else. Specific to this issue is the property that throwing...

Nah, not offended / misconstrued -- more realizing we have like, 5 other issues around this topic. I'm interested in an answer to this thread of questions, as well as...

I'm going to re-open this because I have some thoughts on some not-terrible functionality, inspired by this issue and the recent #170 issue. My thoughts: * Within one dependency graph,...

Duplicate of #164 For now, flyd gives atomic updates without any error handling. Exceptions inside a stream subscription function have no guarantee that any stream in that dependency graph will...

I'm totally up to talk about pluses and minuses for how things should be handled -- my worry about using ended streams is you basically have a dead graph. There...

Reviving this topic. Are we okay with early-out ending when combining on an end stream? How can we have the following behavior work: ``` const myS = getStream().map(x => x...

I dig it, why not make a PR for it as a module?