Limit scope of borrow (automagically)?

[Yohanesu75]

Hi

I made an attempt to use closures within a function for convenience but the borrow checker struck me down… Code example:

pub fn main() {
    let mut i: u32 = 0;
    let mut f = || {
        i += 1;
    };
    f();
    println!("i = {}", i); 
}

This fails because the closure borrow i for the lifetime of main(). What I imagined (with high hopes) would happen was:

pub fn main() {
    let mut i: u32 = 0;
    let mut f = || {
        i += 1;
    };
    // Borrow of i starts here with f() call
    f();
    // Borrow of i ends here

    // Safe to borrow again.
    println!("i = {}", i); 
}

Technically I don’t see any issues with this… Or?

[troiganto]

What you want will be enabled by non-lexical lifetimes, whose stabilization is currently being worked on.

// The only addition:
#![feature(nll)]

pub fn main() {
    let mut i: u32 = 0;
    let mut f = || {
        i += 1;
    };
    f();
    println!("i = {}", i); 
}

Playground link

[Yohanesu75]

Thanks for quick reply!! I knew nll was in the works and I’ve been waiting for it for a long time I wasn’t sure though if this case would also be solved by that.

Awesome!

[Yohanesu75]

What’s the minimum nightly needed for this feature?

[ExpHP]

Even NLL is not so precise. The borrow still starts when the closure is created. The previous example has merely shown how NLL can reason about the “last use” of the mutable borrow.

#![feature(nll)]

pub fn main() {
    let mut i: u32 = 0;
    let mut f = || {
        i += 1;
    };
    println!("i = {}", i);
    f();
}

   Compiling playground v0.0.1 (file:///playground)
error[E0502]: cannot borrow `i` as immutable because it is also borrowed as mutable
 --> src/main.rs:8:24
  |
5 |     let mut f = || {
  |                 -- mutable borrow occurs here
6 |         i += 1;
  |         - previous borrow occurs due to use of `i` in closure
7 |     };
8 |     println!("i = {}", i);
  |                        ^ immutable borrow occurs here
9 |     f();
  |     - borrow later used here

---

What’s the minimum nightly needed for this feature?

That’s hard to say. One could look for the first nightly that added the feature gate, but chances are it doesn’t actually do anything in that version. It’s a feature under active development.

[hyeonu]

Maybe defmac can solve your problem. This crate provides a nice way to declare lambda-like macro. With macro, there’s no lifetime error as they’re not even exist on runtime

[catenary]

This is almost exactly an example in the closures section of the Rust Book, it can be done with regular lexical lifetimes:

fn main() {
    let mut i: u32 = 0;
    {
        let mut f = || {
            i += 1;
        };
        f();
    }
    println!("i = {}", i); 
}

[jjpe]

Be careful, I’ve experimented with NLL and found some ICEs using it. That’s why I’ve turned it back off again. So keep in mind that YMMV when using this unstable feature

[Boscop]

Could NLL theoretically allow this “macro-like” case, too? So that it treats all captured vars as only being borrowed for the duration of the closure call (if the closure doesn’t escape)? I think it would be useful to allow this (if possible) to reduce the need for many such small macros and make these kind of use cases more ergonomic.

[system]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.