Yup- upgraded to [aleph "0.4.2-alpha8"] and it's fixed - thanks again!
On Friday, September 9, 2016 at 8:54:36 PM UTC-7, Alex Miller wrote:
>
> Oh yeah, I fixed that one a while back. :) I think there is a newer
> release of aleph with the change.
>
> On Fri, Sep 9, 2016 at 10:11 PM, Rangel Spa
Hi Sean,
Good point - as you have noticed, my use case is in ClojureScript - I'm
using reagent cursors (hence the deref) fairly heavily to chop my main atom
up and send only the relevant bits to components, but still allow them to
locally modify their state.
In my specific case, I do lookups for
I've worked with a model much like this, and as an experience report: it
resulted in a lot of pain. Atoms inside atoms, or really more than one atom
for the entire state of your app results in to many sources of mutability.
On top of that, you have the problem of async updates: some part of your
st
Most interesting ... a few observations:
1. It is interesting to see how much work is needed to populate the
third output of diff (i.e. the data common to the two inputs)...I'm
wondering how often it's the case that callers really only care about the
differences and not the similaritie
