Parameter type may not live long enough?

by

There are actually plenty of types that can “not live long enough”: all the ones that have a lifetime parameter.

If I were to introduce this type:

struct ShortLivedBee<'a>;
impl<'a> Animal for ShortLivedBee<'a> {}

ShortLivedBee is not valid for any lifetime, but only the ones that are valid for 'a as well.

So in your case with the bound

where T: Animal + 'static

the only ShortLivedBee I could feed into your function is ShortLivedBee<'static>.

What causes this is that when creating a Box<Animal>, you are creating a trait object, which need to have an associated lifetime. If you do not specify it, it defaults to 'static. So the type you defined is actually:

type RcAnimal = Rc<Box<Animal + 'static>>;

That’s why your function require that a 'static bound is added to T: It is not possible to store a ShortLivedBee<'a> in a Box<Animal + 'static> unless 'a="static.

An other approach would be to add a lifetime annotation to your RcAnimal, like this:

type RcAnimal<"a> = Rc<Box<Animal + 'a>>;

And change your function to explicit the lifetime relations:

fn new_rc_animal<'a, T>(animal: T) -> RcAnimal<'a>
        where T: Animal + 'a { 
    Rc::new(Box::new(animal) as Box<Animal>)
}

More Related Contents:

  1. How can I include a module from another file from the same project?
  2. What does “Sized is not implemented” mean?
  3. Deriving a trait results in unexpected compiler error, but the manual implementation works
  4. How do I implement Copy and Clone for a type that contains a String (or any type that doesn’t implement Copy)?
  5. Mutably borrow one struct field while borrowing another in a closure
  6. What makes something a “trait object”?
  7. How do I convert a Vector of bytes (u8) to a string?
  8. Change enum variant while moving the field to the new variant
  9. When is it useful to define multiple lifetimes in a struct?
  10. Can I write an Iterator that mutates itself and then yields a reference into itself?
  11. How to update-or-insert on a Vec?
  12. Lifetime troubles sharing references between threads
  13. How do I include the end value in a range?
  14. How do I specify lifetime parameters in an associated type?
  15. How do I invoke a system command and capture its output?
  16. How to return a string (or similar) from Rust in WebAssembly?
  17. Can I destructure a tuple without binding the result to a new variable in a let/match/for statement?
  18. What is the difference between Copy and Clone?
  19. Is it possible to have stack allocated arrays with the size determined at runtime in Rust?
  20. How to format output to a byte array with no_std and no allocator?
  21. What is the right way to allocate data to pass to an FFI call?
  22. Why does compilation not fail when a member of a moved value is assigned to?
  23. Why does a mutable borrow of a closure through DerefMut not work?
  24. What does “missing lifetime specifier” mean when storing a &str in a structure?
  25. Why can Serde not derive Deserialize for a struct containing only a &Path?
  26. How to quiet a warning for a single statement in Rust?
  27. Use of undeclared type or module `std` when used in a separate module
  28. Is there an elegant solution to modifying a structure while iterating?
  29. How do I cope with lazy iterators?
  30. Can a struct containing a raw pointer implement Send and be FFI safe?

Leave a Comment