Allow the "gles"
backend to (theoretically) compile on no_std
targets.
#7267
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
Part of #6826.
Description
Removes
std
usage from thegles
backend inwgpu-hal
, allowingwgpu-hal
to build onno_std
targets likewasm32v1-none
(once its dependencies, notablynaga
, are allno_std
compatible too).This entirely consists of conditionally replacing
Mutex
withRefCell
, then making sure that this doesn’t accidentally happen if we are also exposingSend + Sync
.I’m not very confident in the design of this change, but I tried to do it in a way which at least doesn’t add any unsound configurations.
Testing
Confirmed the backend still builds on native and wasm, and ran the test suite.
Squash or Rebase?
Rebase
Checklist
cargo fmt
.taplo format
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
cargo xtask test
to run tests.CHANGELOG.md
entry.