How to initialize struct fields which reference each other

by

Not only is there an issue with initialization, there could also be issues with destruction, if GameIterator implemented Drop: the compiler would have to know that it needs to destruct game_iter before game_window, otherwise game_window would have a reference to a destroyed GameWindowGLFW while running its drop() method.

There’s no way to pass the lifetime of the struct itself as a lifetime argument. The only thing you can do is remove the game_window field from MyGame and pass a GameWindowGLFW instance to MyGame‘s initializer. If you want to encapsulate this so that the user doesn’t need to create a GameWindowGLFW, you could write a method that creates a GameWindowGLFW and a MyGame on the stack and calls a closure that accepts a MyGame argument only.

pub struct MyGame<'a> {
    game_iter: GameIterator<'a, GameWindowGLFW>,
    //...
}

impl<'a> MyGame<'a> {
    fn new(game_window: &'a mut GameWindowGLFW) -> MyGame<'a> {
        MyGame {
            game_iter: GameIterator { game_window: game_window },
        }
    }
}

fn start_game(callback: |game: &mut MyGame|) {
    let mut game_window = GameWindowGLFW;
    let mut game = MyGame::new(&mut game_window);
    callback(&mut game);
}

fn main() {
    start_game(|game| {
        /* use game here */
    });
}

More Related Contents:

  1. How do I create a heterogeneous collection of objects?
  2. 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
  3. Is it possible to control the size of an array using the type parameter of a generic?
  4. How do I stop iteration and return an error when Iterator::map returns a Result::Err?
  5. Are polymorphic variables allowed?
  6. Does println! borrow or own the variable?
  7. How do I pass disjoint slices from a vector to different threads?
  8. Efficiently mutate a vector while also iterating over the same vector
  9. How do you unwrap a Result on Ok or return from the function on Err?
  10. What does “mismatched types: expected `()`” mean when using an if expression?
  11. How can I downcast from Box to a trait object type?
  12. How do I ‘pass down’ feature flags to subdependencies in Cargo?
  13. When returning the outcome of consuming a StdinLock, why was the borrow to stdin retained?
  14. Using generic trait methods like .into() when type inference is impossible
  15. Why does an enum require extra memory size?
  16. What is a crate attribute and where do I add it?
  17. Parameter type may not live long enough?
  18. Why does Rust disallow mutable aliasing?
  19. How to store rusqlite Connection and Statement objects in the same struct in Rust? [duplicate]
  20. How to model complex recursive data structures (graphs)?
  21. Why can’t I reuse a &mut reference after passing it to a function that accepts a generic type?
  22. How can I define an async method in a trait?
  23. How do I specify the linker path in Rust?
  24. How can I override a constant via a compiler option?
  25. How do I specify that a struct field must implement a trait?
  26. What does Rust’s unary || (parallel pipe) mean?
  27. How to create and write to memory mapped files?
  28. Downcast traits inside Rc for AST manipulation
  29. How to check in Rust if architecture is 32 or 64 bit?
  30. Is there any way to restrict a generic type to one of several types?

Leave a Comment