Literally every time I port code I wrote in another language to Rust, the Rust code exposes bugs without even shipping it.
-
Could it be that Ruby and Rust are close enough in paradigm that you're able to think in a similar manner, but have the safety net of a type checker + its memory model?
I think that it's primarily the ability to express ownership constraints, which are not optional, regardless of language
-
-
Interesting! I haven't spent any time in Rust to know what you're saying first hand, but that makes sense. Sounds like Rust is a great tool for computational thinking.
-
I’ve been finding bugs too when porting / rewriting in Rust. In at least some cases, cargo-fuzz helped me find integer overflows and the like, so not just ownership.
End of conversation
New conversation -
-
-
Could it also be that you are writing the same code twice and so already know the constraints, rules of the system. Or does it also apply when porting someone else's code?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.