Make initialize_adapter_from_env take a compatible surface #3905
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.
Checklist
cargo clippy
.cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Similar issue as in #3792, initialize_adapter_from_env_or_default ignores backend_bits if WGPU_ADAPTER_NAME is not set
Description
The
initialize_adapter_from_env_or_default
function currently does not respect thecompatible_surface
parameter ifWGPU_ADAPTER_NAME
is set, andinitialize_adapter_from_env
cannot be used with a compatible surface requirement.Let's modify
initialize_adapter_from_env
to take acompatible_surface: Option<&Surface>
parameter, and makeinitialize_adapter_from_env_or_default
use that.Testing
Manual testing in separate project.