Lines Matching +full:crate +full:- +full:example

4 to the `libc` crate.
11 The internal structure of this crate is designed to minimize the number of
13 to all platforms in the future. As a result, the crate is organized
22 platforms of that level. For example, when adding a Unix API it should be added
23 to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
27 at, fear not! This crate has CI support which tests any binding against all
32 symbols list(s) found in the `libc-test/semver` directory. These lists keep
33 track of what symbols are public in the libc crate and ensures they remain
34 available between changes to the crate. If the new symbol(s) are available on
51 We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
53 1. [`libc-test`](https://github.com/gnzlbg/ctest)
54   - `cd libc-test && cargo test`
55   - Use the `skip_*()` functions in `build.rs` if you really need a workaround.
57   - `rustc ci/style.rs && ./style src`
63 `libc` crate successfully. It's annoying to do the equivalent of semver-major versioning
68   - The `since` field should have a next version of `libc`
70   - The `note` field should have a reason to deprecate and a tracking issue to call for comments
77 When Rust removes a support for a target, the libc crate also may remove the support anytime.
82 platform in this crate, the next step is to get that sweet, sweet usage from
86 1. Increment the patch version number in `Cargo.toml` and `libc-test/Cargo.toml`.
87 1. Send a PR to this repository. It should [look like this][example-pr], but it'd
90 1. Once merged, the release will be tagged and published by one of the libc crate
93 [example-pr]: https://github.com/rust-lang/libc/pull/2120