I think I can do a neat trick of guaranteeing conservative MSRV if features are disabled.
With parking_lot feature enabled, I am bound to at least that crate's MSRV, so I can't make promises.
Additionally, at some point, when std::sync::Mutex::new becomes const, I'd like to take advantage of that. I plan to add a defaultstd_once_cell_get_or_try_init feature at that moment, which will bump MSRV if you use default features.
Also, the crate's version is currently 0.2, but, API-wise, I am ready to do 1.0. However I'd prefer to do that later (months?) lest someone finds a critical issue with the current interface.
cc @BurntSushi
I think I can do a neat trick of guaranteeing conservative MSRV if features are disabled.
With
parking_lot
feature enabled, I am bound to at least that crate's MSRV, so I can't make promises.Additionally, at some point, when
std::sync::Mutex::new
becomesconst
, I'd like to take advantage of that. I plan to add a defaultstd_once_cell_get_or_try_init
feature at that moment, which will bump MSRV if you use default features.Also, the crate's version is currently 0.2, but, API-wise, I am ready to do 1.0. However I'd prefer to do that later (months?) lest someone finds a critical issue with the current interface.