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

4 to the `libc` crate.
8 If you want to add your changes to v0.2, please submit them to the `libc-0.2` branch.
18 The internal structure of this crate is designed to minimize the number of
20 to all platforms in the future. As a result, the crate is organized
29 platforms of that level. For example, when adding a Unix API it should be added
30 to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
34 at, fear not! This crate has CI support which tests any binding against all
39 symbols list(s) found in the `libc-test/semver` directory. These lists keep
40 track of what symbols are public in the libc crate and ensures they remain
41 available between changes to the crate. If the new symbol(s) are available on
58 We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
60 1. [`libc-test`](https://github.com/gnzlbg/ctest)
61   - `cd libc-test && cargo test`
62   - Use the `skip_*()` functions in `build.rs` if you really need a workaround.
64   - [`sh ci/style.sh`](https://github.com/rust-lang/libc/blob/main/ci/style.sh)
70 `libc` crate successfully. It's annoying to do the equivalent of semver-major versioning
75   - The `since` field should have a next version of `libc`
77   - The `note` field should have a reason to deprecate and a tracking issue to call for comments
84 When Rust removes a support for a target, the libc crate also may remove the support anytime.
89 platform in this crate, the next step is to get that sweet, sweet usage from
93 1. Increment the patch version number in `Cargo.toml` and `libc-test/Cargo.toml`.
94 1. Send a PR to this repository. It should [look like this][example-pr], but it'd
97 1. Once merged, the release will be tagged and published by one of the libc crate
100 [example-pr]: https://github.com/rust-lang/libc/pull/2120