rust-bindgen

Automatically generates Rust FFI bindings to C (and some C++) libraries.

Libraries & SDKs

Explore on GitHub Read Hacker News discussions

26Distinct people

28Mentions

0Explicit recommenders

5.3KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automatically generates Rust FFI bindings to C (and some C++) libraries.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

mozilla/cbindgen · linked in 5 of the same discussions
dtolnay/cxx · linked in 2 of the same discussions
immunant/c2rust · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year28 dated mentions

Observed mentions: 2016-08-02 13:56:27 UTC to 2025-08-04 15:55:34 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	1	1
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	4	4
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	4	4
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	4	4
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	3	3
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	4	4
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	2	2
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	4	4
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	2	2

What Hacker News says

4 sources

jupp0r·Jun 20, 2021

I really dislike the article, here are some reasons (referencing the numbered arguments in the article). 1. There are many such parsers. Rusts bindgen [1] is one of them, I have written a proprietary one last year. This is pretty common to do for narrow use cases, there just isn't one for "Convert a C API to Ruby".. 2. "Most VM designs I’ve seen are basically just student exercises". Seriously? Create a better on and get rich then! I'm pretty sure Google would pay good money for something better than v8. 3. You can run z/OS on EC2. They do very different things. It's like saying I wish that cars were as simple as a strawberry. 4. "People used to make GUI frameworks which did more than electron apps, looked better and fit in the tens of kilobytes range." That's correct and that's why lots of apps are based on native UI frameworks. For some

Read the rest

use cases, electron seems to hit a sweet spot (mostly not having to write UI for each platform and the web too). If you don't like electron apps, don't use them, most run in the browser too. 5. "Compilers and interpreters should learn how modern computers work." I don't know where to begin here. Modern compilers optimize for latest hardware all the time, one recent example out of thousand others is this [2] where V8 redundantly inserts short functions into memory regions close to the code they are called from in order to get more instruction cache hits. [1] https://github.com/rust-lang/rust-bindgen [2] https://www.techradar.com/news/google-chrome-is-now-dramatic...

In Obvious and possible software innovations

nixpulvis·Jun 20, 2021

Did you just imply that we put the comments of C headers into our types?! Comments are lower than whitespace as far as the compiler should be sure. As I'm sure you are aware https://github.com/rust-lang/rust-bindgen does basically what you want. I'm actually quite curious where exactly rust-bindgen falls short in the eyes of the author. I'm not as familiar with the other FFI libraries the OP linked.

In Obvious and possible software innovations

virtualritz·Apr 26, 2021

I started working on some Rust bindings for this but I'm currently stuck here[0] with some bindgen issue. If anyone wants to help that would be appreciated heaps. [0] https://github.com/rust-lang/rust-bindgen/issues/2035

In Libfive: Solid modeling (CAD) library/tools with Scheme/Python bindings and GUI

tlamponi·Feb 15, 2021

Not really. We wrote a content-addressable-storage backup solution in rust[0], and one consumer is QEMU for doing backups of VMs, so we expose C bindings of our rust code[1] and use them in QEMU[2], effectively having rust async stuff handled by QEMU co-routine library. It wasn't exactly complicate or the like, required a bit of "plumbing code" but that's OK. Allowing to get (relatively) easy C bindings is a goal and feature of rust, at least the project itself provides and maintains the rust-bindgen crate[3][4]. Having a bit bigger and slightly complex project like a backup server done in rust is such a relief compared to C or similar languages. Good speed, fast start up times like C but refactoring is really a breeze lots of safety is guaranteed and more time can be spent on fixing the semantic bugs. [0]: https://pbs.proxmox.com/docs/in

Read the rest

troduction.html#introduction [1]: https://git.proxmox.com/?p=proxmox-backup-qemu.git;a=summary [2]: https://git.proxmox.com/?p=pve-qemu.git;a=blob;f=debian/patc... [3]: https://github.com/rust-lang/rust-bindgen [4]: https://rust-lang.github.io/rust-bindgen/

In LiteSpeed QUIC (LSQUIC) is an open-source implementation of QUIC and HTTP/3