From 791d95e78f44fc148b67a6fc0a149aa348e9a0bd Mon Sep 17 00:00:00 2001 From: Connor Fitzgerald Date: Wed, 4 Dec 2024 01:26:05 -0500 Subject: [PATCH] Changelog --- CHANGELOG.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7521ad5727..8ef55ab321 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -42,6 +42,17 @@ Bottom level categories: ## Major changes +### Refactored Dispatch Between `wgpu-core` and `webgpu` + +The crate `wgpu` has two different "backends", one which targets webgpu in the browser, one which targets `wgpu_core` on native platforms and webgl. This was previously very difficult to traverse and add new features to. The entire system was refactored to make it simpler. Additionally the new system has zero overhead if there is only one "backend" in use. You can see the new system in action by using go-to-definition on any wgpu functions in your IDE. + +By @cwfitzgerald in [#6619](https://github.com/gfx-rs/wgpu/pull/6619). + +### Render and Compute Passes Now Properly Enforce Their Lifetime + +A regression intoduced in 23.0.0 caused lifetimes of render and compute passes to be incorrectly enforced. While this is not +a soundness issue, the intent is to move an error from runtime to compile time. This issue has been fixed and restored to the 22.0.0 behavior. + ### The `diagnostic(…);` directive is now supported in WGSL Naga now parses `diagnostic(…);` directives according to the WGSL spec. This allows users to control certain lints, similar to Rust's `allow`, `warn`, and `deny` attributes. For example, in standard WGSL (but, notably, not Naga yet—see ) this snippet would emit a uniformity error: