Vulkan vs Rust

Vulkan. You know what it is. But why isn't it out yet?

Oh, what do you know, it's because Rust programmers are complaining it's difficult to interface with their FFI because of Rust's lack of unions, so these SJWs are bitching about it to try to change Vulkan's data structures to be less optimized in order to favour Rust.

Rust is fucking garbage and these rustcucks are fucking up what could be a good API.

https://www.khronos.org/message_boards/showthread.php/9649-Official-Vulkan-Feedback-API-for-High-efficiency-Graphics-and-Compute-on-GPUs?p=38243&viewfull=1#post38243

>>45
You're just going to post a question to a thread on page 2 and not bump it?

The big issue is keeping space conserved without blowing up the code or blowing the performance. A canonical, Servo-relevant example: https://gist.github.com/jdm/9900569

This post gives some short summaries on efficient solutions: https://internals.rust-lang.org/t/summary-of-efficient-inheritance-rfcs/494

This post gives a lot of detail on some proposed solutions: https://aturon.github.io/blog/2015/09/18/reuse/

There are so many proposals because people don't want to see it all go to shit like C++. If C unions were that pressing we would see more proposals for it too, but I haven't found any. The only use of unions in Rust would be to interface with C. Variant types are covered by enums and type punning can be done with mem::transmute.