4 ms·
I'm a beginner at rust, but I think this sentiment is correct. I'm finding developing in rust to be similar to the overhead of test-driven development. When I d
by jdblair 8y ago
I'm a beginner at rust, but I think this sentiment is correct. I'm finding developing in rust to be similar to the overhead of test-driven development. When I do TDD, I spend a lot more time getting to my MVP, at the benefit of catching a lot of bugs early and hopefully writing more correct code. Usually with TDD I'm pretty astonished at the code that I think is correct that fails very simple tests.
I have the assumption that once I am fluent in rust, more and more of the first code I write will be accepted by the borrow checker. The analogy is to C, where I don't really have to think consciously about, for example, assigning and dereferencing pointers. When I was a beginner C programmer (many years ago), I would write code and have it SIGSEGV immediately during test. Now that just doesn't happen unless I'm getting WAY too clever.