Jeehoon Kang

In the same spirit with #452, I think custom allocators should also be integrated into the API. It will greatly improve crossbeam's applicability to, e.g., embedded systems programming. But will...

- I wish crossbeam-utils becomes 1.0. I think it has a quite stable API. - I wish crossbeam-epoch doesn't become 1.0 yet. We have many things to resolve, including but...

Actually, I'm planning to propose a large restructuring of crossbeam-queue (and other crates)... :) May I ask if we could decide when to stabilize it after that?

@taiki-e sorry for being confusing. I think crossbeam-utils is good to go for 1.0, but the others are not.

@tomtomjhj would you please look at the CI failures?

@Vtec234 Thanks for reading the code and giving a comment! Yes, I'm also thinking about that. Actually putting deferred functions and deferred deallocation together inside an enum type (`Garbage`) incurs...

A status update: I implemented a series of patches related to this issue in [this branch](https://github.com/jeehoonkang/crossbeam/tree/pebr). - [Using small epoch numbers](https://github.com/jeehoonkang/crossbeam/commit/b7eac1b3d65d29a37c3d8743e7f62eb3a2a49a50): the [Snowflake paper](https://www.microsoft.com/en-us/research/publication/project-snowflake-non-blocking-safe-manual-memory-management-net/) basically describes how to ensure safety...

@tomtomjhj and I just made an article on "supporting hazard pointers and ejection": https://cp.kaist.ac.kr/gc/ Comments and feedbacks are very welcome!

@glaebhoerl Thank you for your interest in our article. 1. Yes, it would have been much better to compare the performance of PEBR and that of Dice et al.'s version...

We just got noticed that this work will be published at [PLDI 2020](https://conf.researchr.org/home/pldi-2020) :) But I'm still not sure how we can upstream our effort to Crossbeam (this repository).