←back to thread

Stop making me memorize the borrow checker

(erikmcclure.com)
177 points signa11 | 1 comments | 16 Nov 24 23:29 UTC | HN request time: 0.2s | source
Show context
wavemode ◴[17 Nov 24 04:08 UTC] No.42161896[source]▶
This persons's problem is pretty clear - Rust is frankly miserable to write code in if you are trying to optimize everything as much as possible. Since this is the default mindspace of C/C++ programmers, the frustration is understandable.

Rust becomes a lot simpler when you borrow less and clone more. Sprinkle in smart pointers when appropriate. And the resulting program is probably still going to have fantastic performance - many developers err by spending weeks of developer time trying to shave off a few microseconds of runtime.

But, if you're a developer for whom those microseconds really do matter a lot, well then you just have to bite the bullet.

replies(2): >>42162053 #>>42162247 #
1. jltsiren ◴[17 Nov 24 05:44 UTC] No.42162247[source]▶
That doesn't match my experience. C++ programmers typically use C++, because using libraries written in C++ from any other language is a miserable experience. It's rare to encounter C++ code with extensive low-level optimizations.

If you are used to C++11 or newer, you should be able to continue writing very similar code in Rust. The only major issue I encountered was the lack of the idea that "because objects A and B have effectively the same lifetime, they can safely store references to each other, as long as..." But if you are used to older versions of C++, trying to write similar code in Rust is going to be painful.