AFAIK, most WGPU maintainership (myself included) is aware of this and wants it, but we haven't prioritized it yet (and we're not sure when we will). I might add as an alternative that we could also accept an error receiver of some kind from client code, like &dyn FnMut(<some-error-type>), instead of forcing collection of errors. The design space still needs to be explored, and consensus still needs to be driven, but we're happy to have it. I'd likely be the one to field such API discussions, so HMU in Matrix or keep replying here if you'd like to get the ball rolling!

CC @udoprog.

@ErichDonGubler I feel I'm not experienced enough in Rust to be able to accurately assess design considerations for different API suggestions, but I definitely have an interest in pushing for this, for the sake of being able to better work with WGSL for my current project.

An error receiver is an interesting idea, but at least for the tooling I'm working on, I'd likely just use it to produce a collection anyway. Are there use-cases that would be underserved by a simple Iterator<Item = WithSpan<ValidationError>>? Perhaps both methods could be supported to avoid the possibility of forcing collection boilerplate?