* Single squashed commit
* Updated changelog
* Fixed stupid changelog thing
* If I have to do this one more fucking time I'm gonna lose it
* Removed some pub(super)'s
* Thing
---------
Co-authored-by: Andreas Reich <r_andreas2@web.de>
* Some stuff worked on
* Works on MSL
* Ready for test 2
* Fix for a thing lol
* Fixed 2 errors
* Fixed DXC
* Add changelog
* Updated CI to hopefully pass on macOS
* Various fixes
* Some final fixes
* CHanged CI
* Update naga/src/front/wgsl/parse/directive/enable_extension.rs
Co-authored-by: atlv <email@atlasdostal.com>
* Thing
---------
Co-authored-by: atlv <email@atlasdostal.com>
Co-authored-by: Connor Fitzgerald <connorwadefitzgerald@gmail.com>
`create_bind_group` populates the `BindGroup::dynamic_binding_info`
field in the order the user specified. This later gets consumed by
validation in passes and bundles `BindGroup::validate_dynamic_bindings`,
in which `dynamic_binding_info` is assumed to be sorted in binding
order. Eek! We're validating the wrong dynamic binding bounds!
Fix this by sorting `dynamic_binding_info` before it gets put into
a `BindGroup`. Document the field with the invariant that it _must_ be
sorted according to binding index order.
- Validate `@blend_src` structs in type validation. The spec requires
validating any struct with `@blend_src` attributes, whether or not
it is used by an entry point.
- Remove `@blend_src`-related interface validation that is
redundant with the type validation.
- Dual-source blending requires that there be a single color
attachment.
* [wgpu-core] add support for optional BG & BGL entries
* [wgpu] allow gaps in bind group layouts
And allow unbinding in the web backend.
* adapt tests
* add changelog entry
* [wgpu] remove generic from `PipelineLayoutDescriptor`
* Make `depth_compare` and `depth_write_enabled` optional
These fields are optional in the WebGPU API. Having them optional in the
wgpu API as well keeps validation logic centralized in wgpu-core.
Fixes#8830
* Remove `DepthStencilStateIdl`
BREAKING CHANGE: Transfer operations are expressed in terms of a start
offset and a size. Trying to store anything else in errors and traces
yields extra complexity and loses clarity. Change
`TransferError::BufferOverrun` so that its `end_offset` field is no
more. Instead, add a `size` field that should only ever be saving off
fields already provided by user operations.
Previously we required that the enable extension be declared and that
the capability be present if the functionality was used, but allowed the
extension to be declared if the functionality was not used.
New cases for some Clippy lints pop up as part of this upgrade that
cannot be done before, listed below. Yuck!
- `clippy::manual_is_multiple_of`
- `clippy::missing_const_for_fn`
- `clippy::useless_nonzero_new_unchecked`
* Changed msl snapshots to use .metal extension
* Made traces use `.metal` extension instead of `.msl`
* Added changelog entry
---------
Co-authored-by: Erich Gubler <erichdongubler@gmail.com>