-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch from lazy_static to once_cell #623
Comments
I'm the one who was in favor of this in tokio and I'm in favor of doing this in crossbeam as well. As discussed in tokio-rs/tokio#3187, there are several benefits. However, I'm not sure how this interacts with loom PR (#487). |
Hmm, I think loom probably could, though it doesn't have such an API today. I think you best bet would be asking over in the tokio Discord in the #loom channel :) |
Since lazy_static has increased the MSRV to 1.40, I will do this without waiting for support on the loom side. |
May be valuable to open a bug on the loom side to track that this is a desired feature :) |
filed tokio-rs/loom#263 |
Any chance we can get new releases of crossbeam-epoch and crossbeam-utils with this? |
Published in crossbeam-epoch 0.9.9 and crossbeam-utils 0.8.9. |
With tokio having switched from lazy_static to once_cell in 0.3, the dependencies on lazy_static are going way down in many of my projects. It would be nice to get rid of it completely in favor of once_cell. Would you be open to a PR?
The text was updated successfully, but these errors were encountered: