You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much of the once_cell crate's API has now been added to std, so ideally we could remove this dependency. This is blocked on std::sync::OnceLock::get_or_try_init being stabilized:
@jimblandy FWIW, if you are not using portable atomic, then probably you don't actually need once_cell crate. Most of the API is now available in std (but not in core), so I am thinking that the primary role of once_cell for the ecosystem right now is exactly to serve as a poly-fill for no-std use-cases.
At the moment, wgpu_core::pool::ResourcePool uses once_cell::sync::OnceCell::get_or_try_init, whose std analog, std::sync::OnceLock::get_or_try_init, is not yet stable.
Much of the
once_cell
crate's API has now been added to std, so ideally we could remove this dependency. This is blocked onstd::sync::OnceLock::get_or_try_init
being stabilized:once_cell_try
rust-lang/rust#109737As the
once_cell
author commented:At the moment,
wgpu_core::pool::ResourcePool
usesonce_cell::sync::OnceCell::get_or_try_init
, whosestd
analog,std::sync::OnceLock::get_or_try_init
, is not yet stable.PRs:
once_cell::sync::OnceCell
/std::sync::OnceLock
(as much as possible) #6400The text was updated successfully, but these errors were encountered: