| commit | 08427ce937f76d368edb35a6a2fae574738db491 | [log] [tgz] |
|---|---|---|
| author | Roopa Sattiraju <sattiraju@google.com> | Tue Dec 21 16:58:27 2021 -0800 |
| committer | Roopa Sattiraju <sattiraju@google.com> | Tue Dec 21 16:58:27 2021 -0800 |
| tree | 8d10e2b81bb9143fc2776d975e681756c4f39ee6 | |
| parent | 24060bc08c0982bef77f38d34d83fe50bf34e104 [diff] |
Adding bluetooth apex Bug: 206121418 Test: Compile Change-Id: I9f6ddf45ddbf0cbb1b5cc0a84dffa17468892416
Nix seeks to provide friendly bindings to various *nix platform APIs (Linux, Darwin, ...). The goal is to not provide a 100% unified interface, but to unify what can be while still providing platform specific APIs.
For many system APIs, Nix provides a safe alternative to the unsafe APIs exposed by the libc crate. This is done by wrapping the libc functionality with types/abstractions that enforce legal/safe usage.
As an example of what Nix provides, examine the differences between what is exposed by libc and nix for the gethostname system call:
// libc api (unsafe, requires handling return code/errno) pub unsafe extern fn gethostname(name: *mut c_char, len: size_t) -> c_int; // nix api (returns a nix::Result<CStr>) pub fn gethostname<'a>(buffer: &'a mut [u8]) -> Result<&'a CStr>;
nix target support consists of two tiers. While nix attempts to support all platforms supported by libc, only some platforms are actively supported due to either technical or manpower limitations. Support for platforms is split into three tiers:
The following targets are supported by nix:
Tier 1:
Tier 2:
Tier 3:
nix requires Rust 1.41.0 or newer.
To use nix, add this to your Cargo.toml:
[dependencies] nix = "0.22.1"
Contributions are very welcome. Please See CONTRIBUTING for additional details.
Feel free to join us in the nix-rust/nix channel on Gitter to discuss nix development.
Nix is licensed under the MIT license. See LICENSE for more details.