Re: [MirageOS-devel] Blog post on Irmin/CueKeeper

[Daniel BÃnzli <daniel.buenzli@xxxxxxxxxxxx>]

Le samedi, 27 juin 2015 Ã 12:32, Thomas Leonard a Ãcrit :
> Hmm, yes, this could be a problem for handlers that expect to see all states.

I wouldn't put it in these terms (handlers, state) but yes it breaks the 
semantics of signals. This needs more thinking.   
  
> S.diff would be a problem too (and sometimes you might want to diff
> against the last seen value of the signal rather than the previous
> actual value).

I don't understand this comment.  
  
> In the case of CueKeeper, it would be an advantage though. For
> example, there are multiple tabs, each of which shows a different
> query. The FRP code (since replaced) was something like this:
>  
> let tab_content =
> S.bind current_tab (function
> | `Process -> process_tab
> | `Work -> work_tab
> ...
> ) in
>  
> The problem was that it recalculated every tab's query each time,
> whereas I only wanted it to calculate the elements for the tab that
> was currently selected.

Isn't this a matter of not creating the queries in the binding function but 
rather outside of it ?  

Daniel



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel