Came across : "rust-gb" which compiles Rust to Game Boy ROMs. To make it work, the author forked both the Rust compiler and LLVM. 🦀 The Game Boy isn't a Rust target. It's not even Tier 3, and there's no stable LLVM backend for its CPU. So the pipeline is: rust-z80, a fork of rustc targeting sm83, emits LLVM-IR. llvm-z80, an LLVM fork carrying a Z80/SM83 backend, lowers that to machine code. Then it links against the runtime and writes a cartridge header. All of it driven by cargo gb build. But the part worth the price of admission is gb-bank. Game Boy cartridges only map a 16KiB window at a time, so you swap banks in and out as the game runs. Holding a pointer into a bank that's since been swapped away is a classic way to corrupt a retro game, and nothing in C stops you doing it. gb-bank makes it a compile error. GhostCell-style tokens mean a pointer into an unmapped bank simply won't type-check. And a #[bank] function returns a Warp, described as the Future analog of a banked call, which you run with .drive(). Using a borrow-checking technique from 2021 to fix a hardware footgun from 1989 is a genuinely lovely idea. Also ships gb-image-fx for converting PNGs into Game Boy tile data, and a set of runnable examples to copy from. The author is upfront that it's early and largely untested outside their own machine. The stated reasons for using Rust here are worth quoting: better grammar than C, strict types that stop you writing incorrect code even on tiny devices, and putting everything aside, it's fun. 🔗 github.com/zlfn/rust-gb #RustLang #GameBoy #Compilers #OpenSource #Retrocomputing