cberner
Don't panic
SessionUnmounter and BackgroundSession have unhandled .lock().unwrap() that causes clippy to complain that there should be a # Panic section in the function documentation. I think it's more appropriate to handle the poison error, rather than panic.
Additionally, some of those functions had an unused io::Result type that can be removed.
To clarify, this PR branches from PR #401 . That one should be merged first. Update: it has been merged.
To clarify, probably, the mutex lock will likely never actually ever become poisoned. There simply isn't any operation currently in use that can fail while holding the lock. So this error handling may never be reached. At least now the warning message in the code clearly demonstrates our intention is to ignore the error.