Open james7132 opened 2 years ago
It looks like CI is stuck on this PR --- not totally sure what's going on there.
Should we report this to GitHub? This seems like it's permanently stuck.
Looks like that was my fault; I changed the CI configuration, and it should run correctly now.
@james7132 are you still intending to finish this (fix the two CI failures)?
Looks like once_cell
uses the 2021 edition, which has a MSRV of 1.56. Is this acceptable to bump the MSRV of this crate? or should I instead pin an earlier one that is compatible with this crate's MSRV of 1.42?
@hawkw ping about this question
@james7132 maybe just update the PR to get it to go green, since this would be a trivial change? Then there's a chance no further back and forth is needed when Eliza finds some time for this again.
With syn 2.0.0
coming out bumping it's MSRV to 1.56, there's likely a bunch of crates bumping their MSRVs soon. Went ahead and updated the MSRV, added a rust_version
field to Cargo.toml, and updated the CI workflow.
Also bumped the edition to 2021.
Loom seems to dislike once_cell
's Lazy implementation. It's apparently unsupported right now, see https://github.com/tokio-rs/loom/issues/263.
Seems like parts of once_cell
have been stabilized into std: https://github.com/rust-lang/rust/pull/105587.
Now that OnceLock is stable another possibility would be to use it instead but keep lazy_static as an optional feature for older compiler support
Although you probably don't want to increase the MSRV that much for now, VecDeque::new()
was made const
in 1.68, so it'll be possible to remove lazy_static
/once_cell
usage altogether at some point.
Any progress on this PR? I'm trying to purge lazy_static
from my dependency tree.
Now that OnceLock is stable another possibility would be to use it instead but keep lazy_static as an optional feature for older compiler support
This would be nice. Could be a default Cargo feature msrvXXXX
that you can disable to get a lighter dependency tree at the expense of requiring a newer compiler.
Fixes #71. Another benefit is that accessing registry's next counter doesn't require an extra lazy check, only on the actual freelist.