Rajesh Malviya

nope, this was related to #337

@garettbass, is this reproducible reliably with wgpu-native? If so, can you also try the wgpu rust examples? ```shell ~> # Install Rust toolchain - https://www.rust-lang.org/learn/get-started ~> git clone https://github.com/gfx-rs/wgpu.git ~>...

The long term plan I had in mind is to use the new [`webgpu.yml`](https://github.com/webgpu-native/webgpu-headers/blob/main/webgpu.yml) to generate all the structs, enums and `extern "C"` functions along with generating a large Trait...

(Apologies for missing this) Tbh instead of this, I would prefer a setup where user can clone the repo (or github's download zip) to a directory and then import that...

Closing this as on web/wasm Emscripten provides it's own `webgpu.h` implementation which binds to the WebGPU JS functions directly. It doesn't make sense for `wgpu-native` to "support" emscripten if user...

#264 implemented the push/pop error scopes, and now most the internal errors are handle-able by error scopes. Some that are categorized as fatal errors, still panic: https://github.com/search?q=repo%3Agfx-rs%2Fwgpu-native+handle_error_fatal&type=code This categorization of...

> If I interpret that search result, the handle_error_fatal function is never called, is it? You have to expand the "Show 19 more matches". Don't know it isn't default in...

#272 migrates from `*Drop` functions to `webgpu.h` `*Reference`/`*Release`. It fixes the problem of `End`/`Finish`/`Submit` functions dropping the related objects, now the library guarantees that they will only be dropped when...

As library migrated from `gfx-rs` to `wgpu-core` a while back. This is probably fixed, if it is still occurring please file a new issue.

This is an upstream `webgpu.h` discussion and as it's already filed there, closing this.