[wgpu-types]: Add cross-platform Mutex
and RwLock
#7830
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connections
no_std
forwgpu-core
#7746Description
Across Wgpu's various crates there is a need for locking primitives, such as
Mutex
andRwLock
. Currently, each crate independently imports from eitherstd
,parking_lot
, or potentially uses aRefCell
-based fallback forno_std
compatibility. This leads to duplicated implementations of the fallback logic. This PR centralizes theseMutex
andRwLock
definitions intowgpu-types
, allowing them to be re-used across Wgpu. Note that while that is the intention of this PR, currently it just adds the types towgpu-types
; it does not switch the various crates to it. I consider this to be a reasonable split to reduce merge conflicts while the design is reviewed.Testing
Squash or Rebase?
Checklist
cargo fmt
.taplo format
.cargo clippy --tests
. If applicable, add:--target wasm32-unknown-unknown
cargo xtask test
to run tests.CHANGELOG.md
entry.