@tef just curious, what are you writing?
@federicomena sketching, not so much writing
but some form of concurrent key-value store eventually, but it has to be built out of so many fiddly parts
the thing i am trying to avoid is locks on the read path, which means some form of garbage collection unfortunately
well, i mean i need to coordinate between threads to know when it's safe to reclaim memory
i could use arc instead, but, that means an increment/decrement on every lookup
what i'm trying to do is much more read copy update/cas
@tef @federicomena that sounds a hell of a lot like what crossbeam does!
@federicomena @tef yep, pretty much that! I should caution that I never could figure out how to use the crossbeam GC correctly (all my single-threaded things ended up leaking memory all over the place), but would love to see an example that works (: