maybe types were a mistake

Fr though this support library uses the Rust type system in a super cool way. Every resource a microcontroller has (clocks, pins, spi, etc) has a type, and setting it up consumes that type

So you can't, for example, initialise a clock twice, or use a pin configured for input on a function that expects an output (like driving an LED)

I'm not super experienced with microcontrollers so this is extremely helpful! And it's all compile-time too: most of these types are zero sized so they don't even show up in the compiled binary

I like rust

And it's real rust too! No Micropythonor TinyGo or whatever, it's the same language I use for websites and Advent of Code, running on a chip so small it doesn't even need a heatsink

This was all going super well until I realised buffering an image for the display would take 50x the memory the system has