Jeehoon Kang

status report: I've changed my mind, and I'm retrying to merge this RFC. As discussed above, hopefully it can fill several entries in the concurrent queue implementation matrix. I revised...

@schets Thanks for your comments! After applying the optimizations you mentioned, I finally managed to get a good performance result :) @stjepang I'm thinking of providing `crossbeam_circbuf::{bounded,unbounded}::{spsc,spmc}` channels in this...

@stjepang yeah, probably we're discussing what should be the API of `crossbeam-queue`. I also don't have a concrete design, but here are my two cents. We already had [a discussion...

I think the proposed nomenclature is more consistent than that of the current implementation. May I ask why `AtomicBox` and `AtomicArc` correspond to `Option` and `Option`, not `Box` and `Arc`?...

I wonder if we can efficiently implement `AtomicBox` and `AtomicArc`. If they don't fit in a single word, we should resort to blocking implementation for portability, right? Can we ensure...

To my eyes, https://github.com/crossbeam-rs/crossbeam-utils/issues/2 suggests that we should not allow users to specify `Ordering` for atomic types, at least for `AtomicBox` and `AtomicArc`. For `AtomicCell`, the only implementation I can...

@spacejam I'm also waiting for DWCAS to land in Rust. It will enable a whole new class of concurrent algorithms, e.g. LCRQ for starters. It was not possible even in...

Actually, I was writing on the same topic :) Thank you for writing up!

Thank you for the valuable comments! I felt we need use cases of Crossbeam we can target on for improving Crossbeam, and elfmalloc is an excellent one. I implemented a...

@joshlf yes, I noticed the use of `try_with` in your example instead of `with`, but I couldn't think of a good implementation of Crossbeam with `try_with`. We may create a...