Re:Rust's 2017 roadmap, six months in
by shmerl on Wednesday July 05, 2017 @05:29PM
(#14706276)
What is the most difficult part for Qt then? Translating some of its concepts in Rust?
[ Parent
| on HN ]
AFAICT, QT has its own implementation of signals and slots (events and event handlers essentially) which is a pain for Rust's ownership model and it also has a code generator that deals with some of C++'s limitations, making it harder to generate usable bindings. If that weren't enough, there is no native (clean) Rust way to do C++ inheritance which is another big pain.
Rust doesn't have a concept of inheritance and overriding which is a pretty key part of the qt design.
If you are okay to use qt out of the box, there are a few bindings. But you won't be able to customise it like you would with actual qt.