Vitaly Shukela
Vitaly Shukela
Currently it is the only unsafe function in my program. Without it (wrapped in thread::spawn instead) user has to manually unmount the system after Ctrl+C'ing the prorgam (which is handled...
`ioctl(TCGETS)` on a file opened from a filesystem implemented with `fuse-rc` causes filesystem to be unmounted: ``` [2019-12-03T13:26:05Z ERROR fuse::request] Unknown FUSE opcode (39) [2019-12-03T13:26:05Z INFO fuse::session] Unmounted /tmp/m ```...
`libfuse` has `fusexmp.c`, so `fuse-rs` should be `examples/xmp.rs`. Supposed to just mirror root filesystem using `libstd`'s `std::fs::*` operations. The example is rather crude and not all operations are supported, but...
I typically use `fusexmp.c` or `fusexmp_fh.c` as a template for creating new FUSE filesystems. It allows to mostly avoid dealing with documentation. Here I see only short `hello` and even...
Is it maintained by original developer? If no, it may be worth to explicitly mark it as unmaintained in README; or invite some other maintainer (i.e. convert Github repo to...
Something like `cargo-script export myfile.csr output/` should write `output/Cargo.toml` and `output/src/main.rs`.
This hack is supposed to increment on each run: ``` rust use std::fs::File;use std::io::Write;fn main(){let c=0; let mut v = vec![]; ::std::io::Read::read_to_end(&mut File::open("q").unwrap(),&mut v).unwrap(); let mut q = &mut File::create("q").unwrap();...
Or shall it stay English-only?
Should delegating to `Deref::deref` be in purview or `ambassador`? If yes, how API should look like? Should it be a special mode of `#[delegate_to_methods]`? Something specified on the trait itself...
Also I see explicit `../target` used inside, which may be fragile if target directory is overridden by `CARGO_TARGET_DIR`.