1
this twitter post is confirmed not statistically sound 1
I'm thankful we had access to it
1
, that's just desktop 
muts are unsafe because you can obtain multiple mut referencesMutex<Option<State>> would probably work? static static DATA: Mutex<Option<Data>> = Mutex::new(None); work for your use-case? 
OnceCell but I need to mutate it more than once
static DATA: Mutex<Option<Data>> = Mutex::new(None); work for your use-case? std::sync::Mutex but not with tokio::sync::Mutex, I'm perhaps just misunderstanding something, but it seems tokios mutexguard doesn't implement DerefMut for some reasonstd::sync::Mutex but not with tokio::sync::Mutex, I'm perhaps just misunderstanding something, but it seems tokios mutexguard doesn't implement DerefMut for some reason std::sync::Mutex but not with tokio::sync::Mutex, I'm perhaps just misunderstanding something, but it seems tokios mutexguard doesn't implement DerefMut for some reason tokio's MutexGuard seems to impl DerefMutstd::sync::Mutex but not with tokio::sync::Mutex, I'm perhaps just misunderstanding something, but it seems tokios mutexguard doesn't implement DerefMut for some reason tokio's MutexGuard seems to impl DerefMut OnceCell
Arc and Mutex there won't be any memory/data race issue's? ' are bloat 's? ' are bloat 'a a>fn<😬a>(hello: 😬a str) -> &😬a str; a is just a namea is just a name &'a
