You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SplitSignal uses side effects in a map over the elements to keep track of which keys have been seen and since the LazyList is evaluated later, it believes no keys were seen and purges all the child signals and calls your project function on every event. You might want another implicit specifically for LazyLists that does a force.
The text was updated successfully, but these errors were encountered:
Thanks, good find! Somehow I've never used LazyList...
I think I'll update the map method of ImmutableSeqSplittable to do something special if the input is a LazyList. Probably convert it to a strict Seq like List or ArraySeq.
SplitSignal uses side effects in a map over the elements to keep track of which keys have been seen and since the LazyList is evaluated later, it believes no keys were seen and purges all the child signals and calls your project function on every event. You might want another implicit specifically for LazyLists that does a force.
The text was updated successfully, but these errors were encountered: