如何获取tokio :: fs :: File :: open的静态路径？

Question

The tokio::fs::File::open(path: T + 'static) requires a 'static lifetime on its path parameter.

This makes sense because it is handled in runtime threads during the program's execution. I think it would make more sense if you could pass your own lifetimes, because the runtime does not need to run the whole time and so you could throw away some stuff. Do I understand something wrong?

I'd like to stay for 'static at the moment and so my problem is this...

I have a trait TraitN and some struct StructX { path: String, } with a fn new(path: &String) -> Box<TraitN> . The new creates and sets self.path = path.to_string(); .

In some impl fn doit(&self) { ... } for StructX , I'd like to call tokio::fs::File::open(&self.path) .

How can I pass &self.path with a 'static lifetime?

This is a complete example:

extern crate futures;
extern crate tokio;
#[macro_use]
extern crate error_chain;

use futures::future;
use futures::future::{loop_fn, ok, Future, Loop};
use futures::Stream;
use std::io::BufReader;
use tokio::{fs, io};

mod error {
    error_chain!{}
}

use error::*;

type FutureResult<T> = future::FutureResult<T, Error>;

trait HandlerTrait {
    fn new(path: &str) -> Box<HandlerTrait>
    where
        Self: Sized;
    fn get_all(&self) -> FutureResult<Vec<String>>;
}

#[derive(Debug)]
pub struct Handler {
    path: String,
}

impl HandlerTrait for Handler {
    fn new(path: &str) -> Box<HandlerTrait> {
        Box::new(Handler {
            path: path.to_string(),
        })
    }

    fn get_all(&self) -> FutureResult<Vec<String>> {
        let file = fs::File::open(self.path.clone())
            .and_then(|file: fs::File| ok(file))
            .wait()
            .unwrap();
        let lines = io::lines(BufReader::new(file));
        ok(lines
            .filter(|line| line.len() > 80)
            .map(|all| all[0..80].to_string())
            .collect()
            .wait()
            .unwrap())
    }
}

fn get_handler(path: &str) -> Option<Box<HandlerTrait>> {
    Some(Handler::new(path))
}

fn get_path() -> FutureResult<String> {
    ok("./somepath/file".to_string())
}

fn start_runtime() -> Result<()> {
    let path: &str = get_path().wait().unwrap().as_str();
    tokio::run(doit(path.clone()));
    Ok(())
}

fn doit(path: &'static str) -> impl Future<Item = (), Error = ()> + 'static {
    let n = 0;
    loop_fn(n, move |_nr| {
        let lh = get_handler(path).unwrap();
        lh.get_all()
            .or_else(|_| Err(()))
            .and_then(|_all| ok(Loop::Break(())))
    })
}

#[test]
fn test() {
    start_runtime().unwrap();
    assert!(true);
}

error[E0597]: borrowed value does not live long enough
  --> src/lib.rs:63:22
   |
63 |     let path: &str = get_path().wait().unwrap().as_str();
   |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^         - temporary value only lives until here
   |                      |
   |                      temporary value does not live long enough
   |
   = note: borrowed value must be valid for the static lifetime...

playground

Answer 1

TL;DR Use a String instead of a &str . This might change when async / await syntax is stabilized.

---

Here's the MCVE I made of your original question:

extern crate tokio; // 0.1.11

trait TraitN {}

struct StructX {
    path: String,
}

impl TraitN for StructX {}

fn new(path: &str) -> Box<TraitN> {
    Box::new(StructX {
        path: path.to_string(),
    })
}

impl StructX {
    fn doit(&self) {
        tokio::fs::File::open(self.path.clone());
    }
}

To solve this, clone the String and give ownership of it to the function:

impl StructX {
    fn doit(&self) {
        tokio::fs::File::open(self.path.clone());
    }
}

---

With your example code, there are numerous problems:

fn start_runtime() -> Result<()> {
    let path: &str = get_path().wait().unwrap().as_str();
    tokio::run(doit(path.clone()));
    Ok(())
}

1. You cannot take a reference to the result of unwrap because nothing will own that value. You cannot have a reference to this kind of temporary.

2. Cloning a &'a str returns a &'a str , not a String .

3. It doesn't make sense to call wait on the value because that blocks the thread. Run everything in the reactor loop.

This function should look like

fn start_runtime() -> Result<()> {
    tokio::run({
        get_path()
            .map_err(|e| panic!("{}", e))
            .and_then(|path| doit(path))
    });
    Ok(())
}

Then all of your code should switch to impl Into<String> instead of &str of &'static str . doit also needs to be able to create duplicate String s:

fn doit(path: impl Into<String> + Clone) -> impl Future<Item = (), Error = ()> + 'static {
    let n = 0;
    let path = path.into();
    loop_fn(n, move |_nr| {
        let lh = get_handler(path.clone()).unwrap();
        lh.get_all()
            .or_else(|_| Err(()))
            .and_then(|_all| ok(Loop::Break(())))
    })
}

this [...] is config which doesn't change [...] read from a configfile during app init.

In that case, create a singleton which will give you an effectively-static value:

extern crate lazy_static; // 1.1.0

use lazy_static::lazy_static;

lazy_static! {
    static ref PATH: String = {
        // Should be read from a file.
        String::from("/the/path/to/the/thing")
    };
}

Then change all of the values to &'static str :

#[derive(Debug)]
pub struct Handler {
    path: &'static str,
}

impl HandlerTrait for Handler {
    fn new(path: &'static str) -> Box<HandlerTrait> {
        Box::new(Handler {
            path
        })
    }
}

And take a reference to the singleton:

fn start_runtime() -> Result<()> {
    tokio::run(doit(&PATH));
    Ok(())
}

You can couple this with phimuemue's answer to get a &'static MyConfigStruct , which could then have a fn foo(&'static self) that is available.

---

There must be something wrong with a language if this becomes so difficult and needs mem-io multiple times.

You are partially correct. It's difficult to have maximally performant async code with today's Rust (1.30) because Rust wants to ensure memory safety above all else. This doesn't mean that the code is unperformant, just that there's a bit of room to do better.

Honestly, making clones here is unlikely to be a performance bottleneck, but it is annoying. That's where async and await syntax comes in. This will allow futures to more easily make use of references in an idiomatic Rust manner.

because the runtime does not need to run the whole time [...] Do I understand something wrong?

However, async and await still might not help you, as by default Tokio will run your future on a different thread. That's one of the primary reasons it requires a 'static bound. This prevents a Tokio thread from having a reference to a stack local that goes out of scope, introducing memory unsafety. This isn't a unique problem to Tokio, however.

See also:

• How can I pass a reference to a stack variable to a thread?
• The compiler suggests I add a 'static lifetime because the parameter type may not live long enough, but I don't think that's what I want
• Why is the bound `T: 'a` required in order to store a reference `&'a T`?
• Why does the Rust compiler request I constrain a generic type parameter's lifetime (error E0309)?

Other bits

It appears that every single call to wait in this code is a misuse of futures. You may wish to re-read the Tokio docs to better understand understand how you are supposed to chain futures. If there's a wait call, it's usually at the end of everything, and even that is rare when using Tokio.

See also:

• How do I synchronously return a value calculated in an asynchronous Future in stable Rust?

Answer 2

You can restrict the lifetime of &self :

impl StructX {
    fn doit(&'static self) {
        // here, we know that self and its members are 'static
    }
}

If you do this, you may actually be better off to have StructX store the 'static borrow of the path in the first place (instead of a string).

Answer 3

I can answer this now by myself:

• fn make_static_str<T>(s: T) -> &'static str where T: Into<String>
• A solution with Arc<Mutex<String>> - The test fails because there is no file to read on playground.