Radar · Rust · Archive · Week 21 · May 18 – 24, 2026
ex_ratatui – Elixir bindings for ratatui via Rustler NIFs
Nice to knowtooling
- What changed
- The crate provides Elixir bindings for the
ratatuilibrary using Rustler NIFs. - Production impact
- The source does not say.
- Try it
- Add
ex_ratatuito an Elixir project and call a Rust function. - Source
- this-week-in-rust.org/blog/2026/05/20/this-week-in-rust-652/
Understand it, then run it
The crate ex_ratatui adds Elixir bindings for the Rust TUI library ratatui. Elixir can call Rust code through NIFs, and ex_ratatui uses the Rustler crate to expose ratatui functions to Elixir. This means an Elixir program can build a terminal UI using Rust’s ratatui without writing Rust code itself. The change is only in the crate; the Rust language or standard library is unchanged.
Run it now
// This program demonstrates that the Rust language has not changed for this crate.
// The ex_ratatui crate is an Elixir binding; it does not compile in Rust alone.
// We simply print a message to show the program runs.
fn main() {
println!("ex_ratatui is an Elixir binding; Rust code alone does not use it.");
}
What it printed when we ran it on Rust 1.98.1 (edition 2024)
ex_ratatui is an Elixir binding; Rust code alone does not use it.
Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.
Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed