foolishly trying to write a data structure in rust

a mutable, concurrent, one

that means handling deletes when other threads might be reading

which requires a mutable, concurrent data structure

@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 (:

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!