file_offset 0.1.1
“Atomically read and write files at given offsets”
imports self::windows::*imports std::fs::File
SHA-2564ad02ed760f100d78f087138613184d8e48d301c97f13804e250773d649900cd
MaleculeMd(In₄)
Evidence
1#[cfg(unix)]
2pub use self::unix::*;
3
4#[cfg(windows)]
5pub use self::windows::*;
6
7#[cfg(unix)]
8mod unix {
9 use std::fs::File;
10 use std::io;
11 use std::os::unix::fs::FileExt;
12
13 #[inline]
⋯12 lines
26 use std::fs::File;
27 use std::io;
28 use std::os::windows::fs::FileExt;
29
30 #[inline]
⋯9 lines
1[package]
2name = "file_offset"
3version = "0.1.1"
4authors = ["Tobias Bucher <tobiasbucher5991@gmail.com>"]
5
6description = "Atomically read and write files at given offsets"
7repository = "https://github.com/tbu-/file_offset"
8license = "MIT/Apache-2.0"
2:29… platform-independent way of atomically reading and
3//! writing files at specified offsets.
4//!
5//! ```
6//! use file_offset::FileExt;
7//! use std:: …
⋯5 lines
14//! ```
15
16use std::fs::File;
17use std::io;
18
19mod sys;
20
21/// This trait provides the extension methods for reading and writing files at
22/// specified offsets.
23///
24/// Note the difference between Windows and Unix behavior listed in the
31:66… independent of
32 /// the current cursor. Note that similarly to `File::read`, returning with
33 /// a short read is not an error. Additionally, read errors that are of
34 /// `ErrorKind: …
No evidence locations were recorded for this file. Raw result