0
I’m learning Rust. And I like playing with software defined radio
(SDR). So the natural project to take on to learn Rust is to
write a crate for making SDR applications. I call it
RustRadio.
I have something that works, and seems pretty OK. But before marking a
1.0.0 release I want to see if I can get some opinions on my use of
the Rust language. Both in terms of design, and more clippy-like
suggestions.
Hence: Roast My Rust. File a github issue, email
me, or tweet at
me. Tell me I’m doing it wrong.
- RustRadio code: https://github.com/ThomasHabets/rustradio
- RustRadio docs: https://docs.rs/rustradio/latest/rustradio/
- The first application: https://github.com/ThomasHabets/sparslog
What my priorities are
There are two API surfaces in RustRadio; the Block API (for writing
blocks), and the Application API (for writing applications that use
blocks). I want them to be good, and future proof, so that I don’t
have to change every block and every application, after adding a
feature or improving the API.
The blocks will need to be thread safe, even though the scheduler is
currently single threaded.
For the streams between blocks I’ll eventually want to make a more
fancy, but unsafe
circular Continue reading