veneer

Crates.ioveneer
lib.rsveneer
version
sourcesrc
created_at2021-08-02 03:21:08.82367
updated_at2024-12-13 19:22:20.923199
descriptionA very thin std-like library that doesn't depend on libc
homepage
repositoryhttps://github.com/saethlin/veneer
max_upload_size
id430223
Cargo.toml error:TOML parse error at line 24, column 1 | 24 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
Ben Kimock (saethlin)

documentation

https://docs.rs/veneer

README

Essentially, a replacement for the Rust standard library on Linux.

The Rust standard library makes tradeoffs in both API and implementation which are generally good but are inappropriate for some uses. This library offers an alternative perspective. In particular, it aims for:

  • No linkage against a libc
  • A minimum of unsafe code outside of that required to write syscall wrappers
  • The lowest runtime overhead possible, even where that makes interfaces awkward

These motivations primarily come from my experience trying to implement a POSIX ls that isn't significantly larger or slower than GNU's ls. For small programs, the accidental complexity of combining Rust's standard library with a libc implementation becomes the dominant contributor of both code size and execution speed.

Commit count: 53

cargo fmt