-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Correct STORAGE_READ_ONLY exclusivity #8490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ErichDonGubler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, just a couple of nits.
CHANGELOG.md
Outdated
| - Removed three features from `wgpu-hal` which did nothing useful: `"cargo-clippy"`, `"gpu-allocator"`, and `"rustc-hash"`. By @kpreid in [#8357](https://github.com/gfx-rs/wgpu/pull/8357). | ||
| - `wgpu_types::PollError` now always implements the `Error` trait. By @kpreid in [#8384](https://github.com/gfx-rs/wgpu/pull/8384). | ||
| - The texture subresources used by the color attachments of a render pass are no longer allowed to overlap when accessed via different texture views. By @andyleiserson in [#8402](https://github.com/gfx-rs/wgpu/pull/8402). | ||
| - The `STORAGE_READ_ONLY` texture usage is now permitted to coexist with other read-only usages. By @andyleiserson in TBD. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The scope of this change isn't a subset of what was affected by the previous change. If there was a conflict between storage-read and constant usage of the same texture view, that would have been rejected even before the previous change, and is now allowed.
That said, it's definitely a minor change, and given that it's been wrong forever without getting noticed, there's a good chance nobody seeing it in the change log will care. But it still seemed like it qualified to be noted in the change log as a bug fix with a distinct user-visible behavior change.
83e5bc1 to
065e1cd
Compare
Fixes #8485
Testing
Adds CTS tests
Squash or Rebase? Squash