Al Liu

> [@matthew-mcallister](https://github.com/matthew-mcallister) Thanks for the explanation. > > I think if we do this before (unreleased) [#1132](https://github.com/crossbeam-rs/crossbeam/pull/1132) is released, we can put in this without a breaking change using the...

I also forked a version of `crossbeam-skiplist` (https://docs.rs/crossbeam-skiplist-fd/0.1.5) to support custom comparators several months ago. If we want to support custom comparators before a new release, I can work on...

> > I also forked a version of `crossbeam-skiplist` (https://docs.rs/crossbeam-skiplist-fd/0.1.5) to support custom comparators several months ago. > > Um, that crate has 9 traits in comparison related...? If they...

> [@taiki-e](https://github.com/taiki-e) [@al8n](https://github.com/al8n) - would be great to get a committer review on [#1182](https://github.com/crossbeam-rs/crossbeam/pull/1182), this would really help us over at SlateDB 😅 I am happy to have those changes...

Hi @notgull, sorry for ping you here. Do you have any idea for this?

> I think it's worth reconsidering the necessity of this feature. Usually if I need to attach some data to a task, I just move it to a future and...

Seems that the data race was caused only by the `CompressionPolicy::High` is enabled, see #38.

I sense that this is caused by contention regarding CAS operation. In the current implementation, the `tower` contains both prev and next pointers, in concurrent write situations, this increases the...

> Hi [@al8n](https://github.com/al8n), thanks for this - this is something I have thought about, and I plan to add this in to the next release of bnum (I've mentioned this...

Hi @notgull, anyone works on this? If not, I would like to give it a try.