3 ms·
How far along is the effort for efficient code reuse (such as filling the gaps of lack of inheritance)? I.e. this: * https://github.com/rust-lang/rfcs/issues/
by shmerl 10y ago
How far along is the effort for efficient code reuse (such as filling the gaps of lack of inheritance)?
I.e. this:
* https://github.com/rust-lang/rfcs/issues/349 https://github.com/rust-lang/rfcs/issues/349
* https://github.com/rust-lang/rust/issues/31844 https://github.com/rust-lang/rust/issues/31844
Is it something coming soon, or it's pretty far still?
- steveklabnik 10y agoSpecialization would only be one piece of the puzzle, and as you can see, it's not in stable yet. All of the bits are still too far out to give a good estimate of.
- shmerl 10y agoThanks. Do you expect that to introduce some non backward compatible changes to language (and for example require a new major version)?
- steveklabnik 10y agoI do not, no, and I would suspect that it'd be a non-starter if it did require it.
- shmerl 10y agoGreat, thanks!
- nercury 10y agoInitial work on specialization has already landed on nightly and is backwards compatible. AFAIK, there are no plans to break that.
- shmerl 10y agoThat's good!