You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all methods that require a native feature will always lead to panic on the WebGPU backend. This is unlike other errors (including lacking features on wgpu-core!) which are funneled through the error callbacks, meaning it's impossible to ignore these errors on WebGPU
Describe the solution you'd like
Ideally, we'd use the same mechanism and invoke the error callbacks. They are right now directly set on the backend so this might would need some additional book-keeping.
Describe alternatives you've considered
Technically we could return a result for all of these cases, but that would make error handling awfully inconsistent.
The text was updated successfully, but these errors were encountered:
Currently, all methods that require a native feature will always lead to panic on the WebGPU backend. This is unlike other errors (including lacking features on wgpu-core!) which are funneled through the error callbacks, meaning it's impossible to ignore these errors on WebGPU
Describe the solution you'd like
Ideally, we'd use the same mechanism and invoke the error callbacks. They are right now directly set on the backend so this might would need some additional book-keeping.
Describe alternatives you've considered
Technically we could return a result for all of these cases, but that would make error handling awfully inconsistent.
The text was updated successfully, but these errors were encountered: