rusty_esp_alloc
The allocator seam: rusty_alloc as the global allocator, with the fixed region a microcontroller needs. One crate, one pin, one decision — declared in a deliverable and never in a library.
Adopting it was one crate and one line, and the first build would have failed on the board without ever failing to compile: the allocator's segment was 32 MiB by default and the region was 220 KiB, and nothing checked. That became an upstream report, and five releases in one week followed, each measured on the chip before it was believed:
| first release | fifth | |
|---|---|---|
| flash it costs | 16.6 KB | 3.4 KB |
| stack it takes | 3,092 B | 4 B |
| region stranded by the granule | 24,576 B | 0 |
The middle row is the one a size table cannot show: memory on the part is fixed, so its sections must sum to a constant, and when they did not the missing bytes were the linker's padding — belonging to no section at all.
Where the evidence is
This crate is part of rusty_esp_core. The
hardware results, the method lines and the open defects live in that package's
README and in
docs/LEDGER.md, where no number
appears without the run that produced it.
Part of Janus
Janus rebuilds the Espressif ESP32 and Arduino application portfolio as independent, memory-safe Rust packages — so a hardware maker can ship a device that the MATA home computer discovers, catalogs honestly, adopts under its own identity, and pays for. Ten packages, three layers, and the dependency direction never reverses.
| layer | packages |
|---|---|
| 0 — the vocabulary | rusty_esp_core · rusty_esp_dsp |
| 1 — the functions | rusty_esp_image · rusty_esp_video · rusty_esp_audio · rusty_esp_signal · rusty_esp_mid · rusty_esp_iroh |
| 2 — the surfaces | rusty_esp_arduino — the sketch facade · espino — the maker's CLI (not published) |
Every package is host-verified against an external oracle and keeps a ledger in which no number appears without the run that produced it. Five of seven device profiles have now run their kill tests on real silicon, three of them over a Wi-Fi network the board hosts itself.
Also check out the rest of Remade With Rust — including
rusty_alloc, the pure-Rust rebuild of
mimalloc that these firmwares run on, and
rusty_jpeg, the JPEG engine behind the
camera path — and our sister project
remade_ffmpeg_rs, a ground-up Rust rebuild of FFmpeg.
About Mata Network
Mata Network builds sovereign, self-hostable infrastructure. Remade With Rust is our open-source home for the permissively-licensed building blocks that work depends on.
License
MIT OR Apache-2.0, at your option. See LICENSE-MIT and LICENSE-APACHE.