Put wgpu's default features behind a "wgpu_default" feature flag #3064
+9
−3
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.
This PR enables users of
iced,iced_rendererandiced_wgputo opt out ofwgpu's default features. It introduces a new feature flag "wgpu_default" that enables the old behavior of enabling thewgpudependency with it's default features. This is included in theiceddefault features to keep the existing behavior for users relying on the previous defaults.This is however a minor breaking change for users who would previously set the "wgpu" flag manually as they would now have to set "wgpu_default" to get the same behavior.
Since
wgpuversion25.0.0the selection of supported backends thatwgpucompiles with can be fully configured via feature flags. This PR enables users oficedand it's supporting crates to manually select what features they want to enable, not being forced in to the defaults.This PR is in the same spirit as #2828 but takes a different approach in naming features while also adding the same features to
iced_rendererandiced_wgpu.