Skip to content

Conversation

@andyleiserson
Copy link
Contributor

@andyleiserson andyleiserson commented Nov 6, 2025

Fixes #8485

  • Update changelog entry with PR link.

Testing
Adds CTS tests

Squash or Rebase? Squash

@ErichDonGubler ErichDonGubler self-assigned this Nov 6, 2025
Copy link
Member

@ErichDonGubler ErichDonGubler left a 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: You mentioned in the issue (#8485) that this was permitted before, but potentially regressed with #8402. Do you think we still need a CHANGELOG entry, if we're just fixing up an issue that hasn't been released yet?

Copy link
Contributor Author

@andyleiserson andyleiserson Nov 6, 2025

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.

@andyleiserson andyleiserson merged commit 3443224 into gfx-rs:trunk Nov 6, 2025
41 checks passed
@andyleiserson andyleiserson deleted the push-uzpruuynlxmv branch November 6, 2025 23:04
andyleiserson added a commit that referenced this pull request Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Combining storage-read with constant in the same usage scope should be permitted

3 participants