John-John Tedro

Feel free to shoot the abstract counter argument, but since you felt mine were too abstract, I'll at least try to rephrase them here more concretely: #### wgpu-core and wgpu-hal...

> Lets elaborate on this, since I certainly don't want to see a rewrite of wgpu-hal. FWIW, changing the signature of every function and every use of `A::*` associated types...

I noticed that you're not removing the [`Buffer` associated type](https://github.com/nical/wgpu/commit/576f28bf0bcfeb43a383da8268f88a8d2d3844c6#diff-797d05eb01678dbe95794b18b0271e468af2cf1e5df45031f08289a157940c12R206) nor the related use of `A: HalApi` in `wgpu-core`, do you intend to keep these?

> Ideally these would go away Isn't it necessary for them to go away to achieve the stated goals? Otherwise I don't see how we're reducing code generation which is...

To clarify, [here's a summary of what produces the most LLVM right now](https://gist.github.com/udoprog/c11f25f8eeafc5fa1cb9ae895af65350) on my system configuration when I build wgpu in release mode. We can see that the more...

> In wgpu-core, an object-safe trait creates the type-erased objects we want. The implementation knows about the concrete hal types so it can place them in the core resource struct,...

I'll leave you to fiddle a bit more, once you have a complete example I can look at it further if you want me to. The tool I've used to...