I have a good theory on the latter symptom (the thread killed
message). Sticking in some traces, as in my appended code, helped me
to see what's going on. It seems to be exactly what you describe --
the variable v is permanently bound to the exception it evaluates
to. Since the right hand
Thanks for the probing, Sterl.
I'm afraid I'm stuck here. Without the more effective thread killing (in
unamb), Reactive seems to be drowning in uselessly running threads. With
improved thread killing, I get many of these false black holes, instead of
computed values.
I don't know whether this
