rustix 0.33.7

Safe Rust bindings to POSIX/Unix/Linux/Winsock2-like syscalls
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

//! Hello world, via plain syscalls.

#[cfg(not(windows))]
fn main() -> std::io::Result<()> {
    // The message to print. It includes an explicit newline because we're
    // not using `println!`, so we have to include the newline manually.
    let message = "Hello, world!\n";

    // The bytes to print. The `write` syscall operates on byte buffers and
    // returns a byte offset if it writes fewer bytes than requested, so we
    // need the ability to compute substrings at arbitrary byte offsets.
    let mut bytes = message.as_bytes();

    // # Safety
    //
    // See [here] for the safety conditions for calling `stdout`. In this
    // example, the code is inside `main` itself so we know how `stdout`
    // is being used and we know that it's not dropped.
    //
    // [here]: https://docs.rs/rustix/*/rustix/io/fn.stdout.html#safety
    let stdout = unsafe { rustix::io::stdout() };

    while !bytes.is_empty() {
        match rustix::io::write(&stdout, bytes) {
            // `write` can write fewer bytes than requested. In that case,
            // continue writing with the remainder of the bytes.
            Ok(n) => bytes = &bytes[n..],

            // `write` can be interrupted before doing any work; if that
            // happens, retry it.
            Err(rustix::io::Error::INTR) => (),

            // `write` can also fail for external reasons, such as running out
            // of storage space.
            Err(e) => return Err(e.into()),
        }
    }

    Ok(())
}

#[cfg(windows)]
fn main() {
    unimplemented!()
}