Update wgpu 0.20 -> 22 #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Once again, the steady march of progress...
wgpu released v22 about a month ago (dropping the "0." prefix and skipping 0.21). I'm updating all my applications to the new version, and vger-rs is a dependency.
Almost no changes were required to vger-rs. v22 of wgpu adds an optional shader cache object to
wgpu::RenderPipelineDescriptorthat we may want to use / expose at some point, but that's it.However while upgrading wgpu doesn't affect our API, it is a breaking change for any downstream application which also makes use of wgpu, which is presumably most. So as before, we should bump vger-rs's release number to 0.4.