__cuervo

5 ms·

1. 1.▲
   Tightness Driven Development in Rust(ecorax.net)

   3 points by __cuervo 5y ago|0 comments
2. 2.▲
   The GPIO war (Low level GPIO drivers in Rust)(ecorax.net)

   6 points by __cuervo 6y ago|1 comments
3. 3.▲
   by __cuervo 6y ago

   I ran into some restrictions for newer accounts, apparently, but a moderator fixed it quickly. Should be all good now!
4. 4.▲
   by __cuervo 6y ago

   That's a risk, yes. For our use case, there is very strict error checking/firmware signature verification on every process involving the flash, so the corruption case is always handled gracefully, leading to a full erase anyway.
5. 5.▲
   by __cuervo 6y ago

   Hey! Author here :) This is a very good question, and you're right that I should've expanded on my rationale as this is not standard practice at all. There are some particularities of the data we're writing that make this cas
6. 6.▲
   by __cuervo 6y ago

   This is exactly what I meant. Thanks Steve for the clear explanation! In the next part of the article I'll hopefully explore some drawbacks of choosing generics all the way down. Either driver would've likely perform a little bett
7. 7.▲
   by __cuervo 6y ago

   Hey! You just made my day. James Mickens (that article in particular) was a huge inspiration, especially the part about crying blood. May have been a bit too dramatic...