swap! on a <-state atom behaves differently from useState about hx HOT 3 CLOSED

I had encountered this before and thought I was using it wrong. Your example was helpful in that it illustrates the difference between useState and <-state.

I believe the problem is that the implementation of ISwap has an implicit dependency on the current value in the Atomified instance. When your initial closure is created with useEffect, it captures that initial value in the atom instance and never gets the updated value.

from hx.

93c43b8 removes the reference of the initial value in the ISwap implementation, fixing this defect.

I'll cut a release later tonight with this change.

from hx.

Nice! Thanks - I'll try it out in my full example but this fix looks good :)

from hx.