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

>>7
Of course it can. This whole thing would be a lot simpler if a discriminating field was in the struct, then it could be wrapped easily.

The people in the thread don't realize what's going on. They think a Rust enum requires storage for all variants. It's not true, only the largest one needs storage, plus discrimination. Discrimination has to exist *somewhere*, and putting it in the struct is the safest bet.

>>10
However, putting it in the program is the fastest, and requires no double checking where the data is consumed. These properties make it preferable to a ``tagged union'', which is what you suggest, and which doesn't appear in C.