[reactive] mappend laziness issue

Sasha Rush sasha.rush at gmail.com
Mon Mar 2 01:46:17 EST 2009


I started playing with reactive again and got stuck on a laziness issue with
mappend. My codes pretty simple, two events controlled by legacy adapters,
one and two. I'm combining them with mappend.

both = one `mappend` two

For some reason the events get clogged up. So for the first "one" event to
fire, a "two" needs to come through, and sometimes vice-versa. It's possible
I'm misunderstanding how mappend works, but the docs make it seem that both
should fire whenever either fires.

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org/pipermail/reactive/attachments/20090301/86f1fa52/attachment.htm


More information about the Reactive mailing list