Hide `pijul lock` and avoid panics when used improperly
[?]
Jan 14, 2021, 8:29 PM
64M73LNCB2V57AWAAKHK2NNERXANMV5V3XI3TFC4XR7FLJNCDCRQCDependencies
- [2]
JL4WKA5PImplement the Sanakirja concurrency model in a cross-process way - [3]
W5NU4F6JLess noisy lock - [*]
SXEYMYF7Fixing the bad changes in history (unfortunately, by rebooting).
Change contents
- edit in pijul/src/main.rs at line 124
#[clap(setting = AppSettings::Hidden)] - edit in pijul/src/commands/lock.rs at line 3
use std::io::Write; - replacement in pijul/src/commands/lock.rs at line 27
.open(&lock.as_ref()).unwrap();.open(&lock.as_ref())?; - replacement in pijul/src/commands/lock.rs at line 31
let listener = UnixListener::bind(&self.path).unwrap();let listener = UnixListener::bind(&self.path)?; - replacement in pijul/src/commands/lock.rs at line 109
let lockfile = OpenOptions::new()if let Ok(lockfile) = OpenOptions::new() - replacement in pijul/src/commands/lock.rs at line 113
.unwrap();lockfile.unlock().unwrap_or(());{lockfile.unlock().unwrap_or(());} - replacement in pijul/src/commands/lock.rs at line 129
.open(lock.as_ref()).unwrap();.open(lock.as_ref())?;