Unable to handle shader compilation errors

[Herschel]

wgpu currently has no API to inspect errors when compiling a shader module. On desktop, Device::create_shader_module will panic on error. On web, the different browsers will print out error info to the console, but execution continues, and errors will usually occur later during pipeline creation with the errored ShaderModule objects.

The WebGPU spec requires a GPUShaderModule.compilationInfo() method that should return any errors generated during compilation.

Ideally, either:

• change Device::create_shader_module to idiomatically return a Result,
• or match the spec and add a ShaderModule::compilation_info method. The user can then inspect this info and return an error as appropriate.

[kvark]

create_shader_module follows the same logic as all the other methods that could fail - it triggers the error on the device. The default handler panics, but you can set your own handler -

wgpu/wgpu/src/lib.rs

Line 314 in 5f1b3e5

fn device_on_uncaptured_error(

compilation_info isn't implemented yet, and we definitely need this.

As for Result, we need to land @pythonesque work first and then see.

[Herschel]

Thanks for the tip about onUncapturedError! Unfortunately looks like it's a TODO on wgpu web backend.

[michael-brennan2005]

Sorry if this isn't the right etiquette, but is there any current work being done to implement compilation_info? This is presenting an obstacle to the renderer I'm working on currently.

[Wumpf]

not that I know of no. But there's also some movement on the Naga side on how errors should be handled #4429

[stefnotch]

I would love to take on this issue.

[stefnotch]

The PR for this is up at #5410, and am happily awaiting reviews