What about being more specific about the error?

[devprofile98]

Hi,
I have been updating my project from an old version of wgpu-native to the latest version lately. The process of migrating was time-consuming, considering several factors ( my project's bad codebase, ancient WEBGPU library, and ... ).
But some of these errors could have been fixed a lot more easily if the error message ( panic!("...") ) were more verbose about where this is happening, considering this project is changing fast and doesn't guarantee a stable API.
Even if the API was stable, it could help to debug developers to identify problems faster, for example, what about printing the binding number in this panic message? I think it would be a great help.

Or another, less severe case, I think it is possible to specify which attachment is causing this error:

Caused by:

  In wgpuCommandEncoderBeginRenderPass, label = 'render pass'

    Read-only attachment with load

Catching these errors is a great help for someone new to this topic, like me. Compared to OpenGL, I think it would be great if we could make The Error message more verbose.

Thank you.

[lisyarus]

Stumbled upon this as well, the error message is extremely confusing.

[lisyarus]

I added a pull-request with a better error message to gfx-rs/wgpu: gfx-rs/wgpu#8068

[lisyarus]

See also the pull request to fix how wgpu-native handles read-only: #497

[devprofile98]

I have also added a PR to print the binding number in panic messages.