4 ms·
* Operator overloading: already in Rust * Standard library user-provided allocators: in nightly, on their way to stable * Move constructors: not in for techni
by steveklabnik 6y ago
* Operator overloading: already in Rust
* Standard library user-provided allocators: in nightly, on their way to stable
* Move constructors: not in for technical reasons and performance reasons, not for approachability
* Inheritance: not in for technical reasons combined with a lack of demonstrated need rather than just desire, not for approachability
* Certain kinds of specialization: you're hedging with "certain", but specialization is in nightly, and used in the standard library.
* SFINAE: Rust doesn't use templates, so this as a direct feature doesn't make sense. I'm not aware of any proposal to include something similar in Rust, the team has never said that this wouldn't be in for approachability
> Somebody who knows Rust better, and C++, will be able to supply a longer list.
I don't think your thesis is accurate, so I don't think so. And if this is so obvious, as you claim, then you should be able to provide examples!