News for hackers. Stuff that matters.
Re:Linux kernel in-tree Rust support by zozbot234 on Saturday July 11, 2020 @06:55AM (#23801127)
Rust generally uses function/method polymorphism based on traits (aka type classes), that's far less prone to overuse and abuse than overloading in C++.
Re:Linux kernel in-tree Rust support by hellofunk on Saturday July 11, 2020 @01:55PM (#23804144)
Is this form of polymorphism done at runtime and thus incurs a similar overhead to the C++ virtual?
Re:Linux kernel in-tree Rust support by steveklabnik on Saturday July 11, 2020 @02:05PM (#23804227)
There are two ways of doing it. The way most people use most of the time does not, it's statically dispatched. The other way is dynamically dispatched, though there are some differences from the way that C++ virtual works. They should be roughly the same in that case, though.
Re:Linux kernel in-tree Rust support by estebank on Saturday July 11, 2020 @02:09PM (#23804255)
It depends, you have access to both capabilities. By default if you're only dealing with an impld trait then it will use static dispatch. If you are passing around that same object as a trait objects, it will use dynamic dispatch and you can also impl Traits on other traits, which are always used as trait objects (vtable) but that have some restrictions on what they can look like. If you rely on the Deref trait to make it look like you have inheritance (but in reality it is composition) it will be the same as the later using dynamic dispatch.
Re:Linux kernel in-tree Rust support by fluffything on Monday July 13, 2020 @03:46AM (#23818178)
You can pick whether you want to do this at run-time or compile-time. The default is compile-time.