Struct ChatStateHandle 

pub struct ChatStateHandle;

The account’s chats and profiles in memory.

Locking resolves the session THIS work belongs to, so a task bound by crate::db::spawn_bound reaches the state of the account it started under — for its whole life, whoever logs in meanwhile. A swap installs a fresh session, and with it a fresh state; the previous account’s is dropped with the session rather than cleared field by field.

Deliberately a handle rather than the Mutex itself: STATE.lock().await reads the same at every call site, and cannot be hoisted into a static or a long-lived struct where it would freeze one account’s state in place.

Implementations

impl ChatStateHandle

pub async fn lock(&self) -> OwnedMutexGuard<ChatState>

pub fn try_lock(&self) -> Result<OwnedMutexGuard<ChatState>, TryLockError>

For callers that must not block — notably Android’s WebView threads, which have no tokio runtime.