3 ms·
It's not that it isn't tedious, but the workflow is a lot more reliable. Refactor, `cargo check`, fix the errors, repeat. When there are no more errors, it is v
by dgunay 4y ago
It's not that it isn't tedious, but the workflow is a lot more reliable. Refactor, `cargo check`, fix the errors, repeat. When there are no more errors, it is very likely the code will still work.
I would say C++ is mostly the same experience, with the exception of anything involving memory safety & lifetimes. It can't guarantee you didn't accidentally introduce a use-after-free/move or anything else of that nature.
- taberiand 4y agoThat's a huge benefit though - I'm more than happy to slowly and methodically refactor a system if at the end of it I can be nearly 100% certain that I haven't inadvertently broken something in the process. The time spent upfront is multiplied time saved in fixing bugs in production. In a tortoise and hare race, sprinting off quickly doesn't count if you can't reliably reach the finish line.