4 ms·
> A huge chain of dependencies. Security issues aside, I prefer my embedded code to be lean and clean. Where does your limit go for that? I wrote a eurorack m
by algesten 5y ago
> A huge chain of dependencies. Security issues aside, I prefer my embedded code to be lean and clean.
Where does your limit go for that? I wrote a eurorack modular embedded thing on Teensy 4.0 (imxrt) in Rust this year. I just inspected the dep tree, it's 38 crates, with 1 being my own.
https://gist.github.com/algesten/9617fc795f2fc94009f1ed311b1d21b2 https://gist.github.com/algesten/9617fc795f2fc94009f1ed311b1...
It was a joy to write this in Rust, I look forward to my next project. This was done with "stable" (not nightly).
- formerly_proven 5y agoHow does cortex-m v0.6.7 manage to depend on cortex-m v0.7.3?
- eldruin 5y agoThat's a way to avoid complicated coordinated upgrades across the ecosystem if certain conditions are met. It's called the "semver-trick" [1]. [1]: https://github.com/dtolnay/semver-trick https://github.com/dtolnay/semver-trick
- pornel 5y agoCargo has its own interpretation of semver: first non-zero number is the major version, so v0.6 is like v6.0.0 and v0.7 is like v7.0.0. Then each major version is treated as a separate crate, as if it was cortex-m-v6 and cortex-m-v7.