flize implements epoch-based reclamation with less restrictions than crossbeam-epoch.
A primary goal of this crate so to have a very rusty API and to have clear and simple source code.
We have an MSRV of 1.36 and increasing it is considered a breaking change.
Furthermore as made evident in the testing benchmarks flize is significantly less vulnerable hitting cases of unoptimized behaviour and unacceptable usage of memory than crossbeam-epoch. In our testing flize is much more consistent in resource usage than crossbeam-epoch.
This crate is useful if you have resources that require destruction in a concurrent environment and you don't want to pay the price of locking.
