4 ms·
My understanding was that implementing this is dependent on MIR fully landing, is that correct?
by untothebreach 10y ago
My understanding was that implementing this is dependent on MIR fully landing, is that correct?
- steveklabnik 10y agoIn an extremely strict sense, no, but in reality yes. MIR makes it so much easier to implement a feature like this that we will wait for it before adding this.
- TylerE 10y agoSo is it likely that this will be a Rust 2.x kind of thing?
- steveklabnik 10y agoNot at all. MIR is not user-facing, it's a refactoring of compiler internals, and it's getting close to being finished. The reason Niko wrote this blog post was to start thinking about the eventual RFC to specify exactly how they should work. There are no current plans for a Rust 2.0.
- kibwen 10y agoNope, nowhere near that far off. MIR will be landing this year, and while we don't have a timeframe for NLL yet it's definitely a priority and it's clear that the devs are giving thought to it, as per this post.
- GolDDranks 10y agoNot at all – 2.0 means a breaking change, but currently the borrow checker is just too restrictive. Loosening it a bit won't be a breaking change, as it allows strictly more code, not less. The landing of MIR is an implementation detail (a quite large at that, but nevertheless), and it shouldn't have any observable effects. (Except for maybe some bugs getting fixed.)