4 ms·
>it seems to be easier to accidentally write extremely slow code in rust than it is in go Never felt about it this way.
by rat9988 6y ago
>it seems to be easier to accidentally write extremely slow code in rust than it is in go
Never felt about it this way.
- baq 6y agolikely depends on your background; if you come from GC languages and are used to everything-is-a-reference, you might end up surprised that Copy types are a thing. right after that you might want to box everything so .clone() works everywhere when you find that some types aren't Copy.
- empath75 6y agoYeah it’s definitely around using clones everywhere.
- masklinn 6y agoI don't know that clones are problems in and of themselves rather than what they do behind the scenes: allocations. Cloning an Rc is completely innocent, cloning a HashMap<String, Vec<String>> is deadly in a way you may not expect if you're used to shallow-copying hashmaps (or even deep-copying them). And it's true that if you think of allocations as being no big deal unless you're aiming for very high performance, your Rust is going to be slow (also your C++ and your C).