rust - What is the correct method for true statics in a single thread application - Stack Overflow

admin管理员组

文章数量:1350331

Assuming I want a static mutable variable that can be accessed anywhere in a single threaded application, with objects in that variable also needing to access it. I am trying to develop a little application to help me fully grasp rust and I cannot find a satisfying way to access statically shared resources and I came up with the following:

static mut WORLD : World = World::new();

#[allow(static_mut_refs)]
fn main() {
    unsafe{
        WORLD.load();
        loop {
            WORLD.player.act();
            match WORLD.state {
                WorldState::Stop => {
                    println!("WORLD STOP");
                    break;
                }
                _ => {}
            }
        }
    }
    println!("Thanks for playing");
}

I cannot use a mutex because in this example the player object may also lock the mutex, but because it is already being accessed from the mutex it locks. Passing a reference around with a reference with Rc seems silly. I think a refcell parent/child setup might be acceptable. I also understand most of these restrictions for unsafe and static_mut_refs are for multi-threading protection, but this is not multi-threaded. I feel there must be a solution I have overlooked.

本文标签： rustWhat is the correct method for true statics in a single thread applicationStack Overflow