I'm having lifetime issues with a particular function in my code. I'm following a tutorial in an attempt to learn Rust and SDL. The tutorial was slightly older and the SDL library has changed since its been written, so I'm following along while also adapting it towards the latest version of Rust-SDL.
The lifetime problem is in this function:
pub fn ttf_str_sprite(&mut self, text: &str, font_path: &'static str, size: i32, color: Color) -> Option<Sprite> {
if let Some(font) = self.cached_fonts.get(&(font_path, size)) {
return font.render(text).blended(color).ok()
.and_then(|surface| self.renderer.create_texture_from_surface(&surface).ok())
.map(Sprite::new)
}
//::sdl2_ttf::Font::from_file(Path::new(font_path), size).ok()
self.ttf_context.load_font(Path::new(font_path), size as u16).ok()
.and_then(|font| {
self.cached_fonts.insert((font_path, size), font);
self.ttf_str_sprite(text, font_path, size, color)
})
}
particularly with the line self.ttf_context.load_font(Path::new(font_path), size as u16).ok()
. The commented line above it is the old SDL version's font loading method.
error[E0495]: cannot infer an appropriate lifetime for autoref due to conflicting requirements
--> src\phi/mod.rs:57:26
|
57 | self.ttf_context.load_font(Path::new(font_path), size as u16).ok()
| ^^^^^^^^^
|
help: consider using an explicit lifetime parameter as shown: fn ttf_str_sprite(&'window mut self, text: &str, font_path: &'static str,
size: i32, color: Color) -> Option<Sprite>
The struct object for that implementation looks like this:
pub struct Phi<'window> {
pub events: Events,
pub renderer: Renderer<'window>,
pub ttf_context: Sdl2TtfContext,
cached_fonts: HashMap<(&'static str, i32), ::sdl2_ttf::Font<'window>>
}
The method is trying to load a font from Phi's ttf_context
and load it into the hashmap. The Rust compiler suggested I add a lifetime to self
in the function parameters, which, when I did that, caused a cascading effect to adding lifetimes to every method calling the original one, all the way down to main()
and didn't help anything.
Since I'm still new to Rust, I'm not sure where the lifetime conflict resides or why this is happening. As a guess, I'm thinking that the Font
object that is being generated is supposed to die with the end of that method but instead it's being loaded into a hashmap with a lifetime of 'window
and those two conflict. I don't know enough about Rust to fix that, though, or if that's even correct.
Here's a smaller example that reproduces the problem:
The problem is indeed that you have constructed an impossible case. Specifically, the code states these points:
Phi
is going to include a reference to aWindow
. That referred-to value lives for the lifetime'window
.Phi
is going to include aFont
, which contains a reference. That referred-to value lives for the lifetime'window
.FontLoader
returns aFont
which contains a reference to a value with the lifetime of the loader. This is due to lifetime inference, which when expanded looks like:Then the code attempts to load a
Font
from theFontLoader
inPhi
, which does not have the lifetime'window
and store thatFont
intoPhi
.FontLoader
(and thusFont
) does not live long enough, so it cannot be stored inPhi
.The compiler has correctly prevented incorrect code.
Your next attempt would probably be to introduce a second lifetime:
This will actually compile, but probably doesn't do what you want. See Why can't I store a value and a reference to that value in the same struct? for further information.
More likely, you want to take a reference to the font loader:
Here, I've renamed the lifetime as it isn't strictly for the window anymore.