search

crossbeam-rs / rfcs

RFCs for changes to Crossbeam
Apache License 2.0
147 stars 14 forks source link

Crossbeam manifesto #7

Open jeehoonkang opened 7 years ago

jeehoonkang commented 7 years ago

I just read @ticki's blog post that advocates hazard pointers (http://ticki.github.io/blog/fearless-concurrency-with-hazard-pointers/), and @stjepang's comment on it in reddit (https://www.reddit.com/r/rust/comments/6qz9p2/conc_an_efficient_concurrent_reclamation_system/dl20t02/).

Which makes me think that maybe it would be great to document why EBR, and when to use it. In other words, I am suggesting an update on @aturon's blog post, which will serve as the Crossbeam manifesto. I hope we can produce such a document via an RFC process.

ticki commented 7 years ago

Yeah, definitely a good idea. My blog post isn't meant to "advocate for", because there are many times where ERB is fine. A how-to-choose guide would be interesting though.

Firstyear commented 7 years ago

Having both available inside of crossbeam would probably be a good option too, because then structures could be build using the choice of EBR or HP that suited correctly.