Lines Matching +full:use +full:- +full:libc

3 In order to achieve our goal of wrapping [libc][libc] code in idiomatic rust
16 [kacl]: https://github.com/olivierlacan/keep-a-changelog/tree/18adb5f5be7a898d046f6a4acb93e39dcf40c…
18 ## libc constants, functions and structs
20 We do not define integer constants ourselves, but use or reexport them from the
21 [libc crate][libc].
23 We use the functions exported from [libc][libc] instead of writing our own
26 We use the `struct` definitions from [libc][libc] internally instead of writing
27 our own. If we want to add methods to a libc type, we use the newtype pattern.
31 pub struct SigSet(libc::sigset_t);
38 When creating newtypes, we use Rust's `CamelCase` type naming convention.
46 constant value from `libc`.
55     pub struct ProtFlags: libc::c_int {
75 ## Structures Initialized by libc Functions
77 Whenever we need to use a [libc][libc] function to properly initialize a
78 variable and said function allows us to use uninitialized memory, we use
84 [enum]: https://doc.rust-lang.org/reference.html#enumerations
85 [libc]: https://crates.io/crates/libc/
86 [std_MaybeUninit]: https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html