rust-mmap
rust-mmap copied to clipboard
rbranson
I cross compile a win_x86_64 and get an error on MemoryMap::new(): ``` error[E0061]: this function takes 1 argument but 0 arguments were supplied --> /home/shellchocolat/.cargo/registry/src/github.com-1ecc6299db9ec823/mmap-0.1.1/src/lib.rs:324:26 | 134 | ErrVirtualAlloc(i32), |...
I get a `cargo audit` warning as `perfcnt` depends on your crate and you use the `tempdir` crate: https://github.com/jbreitbart/criterion-perf-events/issues/2 I also fixed a few clippy/linter warnings.
I am not an expert on `libc`, so can't tell if this is a standard option, but it makes a massive difference on Mac. Reproducer: https://stackoverflow.com/questions/58366166/performance-analysis (Go program is provided...
It seems like this crate is unmaintained and the rust community has aligned around the memmap crate. Is there any reason not to deprecate this crate in favor of the...
Hi, I don't know why I can't compile 'mmap', it has this problem:  I use windows. and my rustc version is "rustc 1.17.0", and cargo version is "cargo 0.18.0"...
Such as in the case of allocating memory from specific hardware addresses (with /dev/mem, or a custom driver), or of a file into the process.
As this crate doesn't expose any of the libc types externally, I believe a patch version bump should be sufficient.
