mermaid-cli 0.5.1

use std::sync::{Arc, Mutex};
use tracing::warn;

/// Extension trait for Mutex to provide safe lock operations
pub trait MutexExt<T> {
    /// Lock the mutex, recovering from poison errors
    /// This is safer than unwrap() as it handles poisoned mutexes gracefully
    fn lock_safe(&self) -> T
    where
        T: Clone;

    /// Lock the mutex for mutation, recovering from poison errors
    fn lock_mut_safe(&self) -> std::sync::MutexGuard<'_, T>;
}

impl<T: Clone> MutexExt<T> for Mutex<T> {
    fn lock_safe(&self) -> T {
        match self.lock() {
            Ok(guard) => guard.clone(),
            Err(poisoned) => {
                // Mutex was poisoned due to a panic in another thread
                // We can still access the data, but we log the issue
                warn!("Mutex was poisoned, recovering data");
                poisoned.into_inner().clone()
            },
        }
    }

    fn lock_mut_safe(&self) -> std::sync::MutexGuard<'_, T> {
        match self.lock() {
            Ok(guard) => guard,
            Err(poisoned) => {
                // Mutex was poisoned, but we can still get the guard
                warn!("Mutex was poisoned, recovering guard");
                poisoned.into_inner()
            },
        }
    }
}

/// Safe lock for Arc<Mutex<T>> - standalone function since we can't impl on Arc
pub fn lock_arc_mutex_safe<T>(mutex: &Arc<Mutex<T>>) -> std::sync::MutexGuard<'_, T> {
    match mutex.lock() {
        Ok(guard) => guard,
        Err(poisoned) => {
            warn!("Arc<Mutex> was poisoned, recovering guard");
            poisoned.into_inner()
        },
    }
}