What should I work on next for device-driver?
Open to suggestions! There's a bunch of stuff in the backlog
XFEDI
ActivityPubRemote profile
Posts
To update, run:
> cargo install device-driver-cli
Then head over to https://marketplace.visualstudio.com/items?itemName=diondokter.device-driver and install the vscode extension
I have UI tests, but that's a kinda blunt weapon.
Ideally I'd be able to spawn some MIR from source and then assert certain properties hold before/after certain MIR passes.
Rustc has some nice infra for this: https://github.com/rust-lang/rust/blob/a7c37f9f0ee5e93396106e9de20f4a86b4154e63/tests/ui/async-await/async-await.rs#L1-L9
I really need a crater-like tool for device-driver to make sure new releases don't break anyone. Went through some existing drivers manually and found 2 bugs!
That said, I feel like the codebase has grown bigger than the current test infra can handle, so I need to improve that too