| commit | badb49277dddf1ea5d407075f9deea48897b52df | [log] [tgz] |
|---|---|---|
| author | bors-servo <lbergstrom+bors@mozilla.com> | Sat Oct 13 18:22:45 2018 -0400 |
| committer | GitHub <noreply@github.com> | Sat Oct 13 18:22:45 2018 -0400 |
| tree | 4b39c803a0135ff0195ce50d9f4f48703c9aa3e5 | |
| parent | a77b136f436e2e77d7cb67cd439f8fba33b71570 [diff] | |
| parent | 5b225971afe1eb672b8f3f5b357dfe3aa8b419a9 [diff] |
Auto merge of #1420 - jcreedcmu:jcreed/blacklist-identifier, r=emilio Re-add ability to blacklist arbitrary identifiers (regardless of which sort of Item they are) @emilio how about this? If you're trying to move away from allowing `Item`-type-independent blacklisting on purpose, I'd understand, but this seemed like the easiest fix to let remacs bump their bindgen version up to master. I also considered adding a `blacklisting_callback` that let the caller supply a `fn (item: &Item) -> bool` to blacklist however they want, but it seemed somewhat unpleasant to make the client recapitulate the whole build-up-a-vector-of-strings-and-map-over-them-checking-if-they-match-as-regexes that bindgen is already supplying.
bindgenimpl period has been started! Join us at Gitter.im.
bindgen automatically generates Rust FFI bindings to C (and some C++) libraries.
For example, given the C header doggo.h:
typedef struct Doggo { int many; char wow; } Doggo; void eleven_out_of_ten_majestic_af(Doggo* pupper);
bindgen produces Rust FFI code allowing you to call into the doggo library's functions and use its types:
/* automatically generated by rust-bindgen */ #[repr(C)] pub struct Doggo { pub many: ::std::os::raw::c_int, pub wow: ::std::os::raw::c_char, } extern "C" { pub fn eleven_out_of_ten_majestic_af(pupper: *mut Doggo); }
📚 Read the bindgen users guide here! 📚
API reference documentation is on docs.rs