Files

Basti Ortiz 1d895b8dfc refactor(capi): make early returns consistent in C examples (#2812 )

- Since the `if` condition already causes the loop to `break`,
  the `else` is not necessary. We wouldn't have reached the `else`
  block, anyway, if the prior `if` condition passed.
- We are more likely to poll a successful chunk than finish
  the request or throw an error. Thus, it is best if we go
  for the optimistic route and check for the successful
  case first.

2022-04-11 17:20:14 -07:00

examples

refactor(capi): make early returns consistent in C examples (#2812 )

2022-04-11 17:20:14 -07:00

include

docs(ffi): expand URI documentation

2021-09-16 10:20:40 -07:00

cbindgen.toml

chore(ffi): run gen_header.sh in CI environment (#2488 )

2021-04-06 14:46:14 -07:00

gen_header.sh

chore(ffi): update gen_header script to use unpretty option

2021-08-04 11:45:03 -07:00

README.md

docs(ffi): document nightly requirement for FFI

2022-03-03 15:05:42 -08:00

README.md

C API for hyper

This provides auxiliary pieces for a C API to use the hyper library.

Unstable

The C API of hyper is currently unstable, which means it's not part of the semver contract as the rest of the Rust API is.

Because of that, it's only accessible if --cfg hyper_unstable_ffi is passed to rustc when compiling. The easiest way to do that is setting the RUSTFLAGS environment variable.

Building

The C API is part of the Rust library, but isn't compiled by default. Using a nightly release of cargo, starting with nightly-2022-03-02, it can be compiled with the following command:

RUSTFLAGS="--cfg hyper_unstable_ffi" cargo +nightly rustc --features client,http1,http2,ffi -Z unstable-options --crate-type cdylib