The most important distinction in a language is

whether it has GC or not.

>>19

No, take a look at the vulkan thread.

That was literally one guy complaining because he was trying to write his own bindings and didn't know how to make it work. If he was serious about his project he would have just used the unsafe memory manipulation functions in the Rust standard library, like everyone else does (at least until a convenient solution is available).

Point being, it's not that Rust is incapable of doing certain things. It's just that this one guy didn't know how to do them.

>>42

It's just that this one guy didn't know how to do them.

It's a little more than that. He needed to provide the functionality in a seamless way to library consumers without adding overhead. It can be done, but you end up with a convoluted solution and will have to rely on the optimizer to fix it up for you. He should complain, but not at the Vulkan people, except about the actual API deficiencies.