3 ms·

Reference counting and locks often is the easy path in Rust. It may not feel like it because of the syntax overhead, but I firmly believe it should be one of th

Reference counting and locks often is the easy path in Rust. It may not feel like it because of the syntax overhead, but I firmly believe it should be one of the first solutions on the list, not a last resort. People get way too fixed on trying to prove to the borrow checker that something or another is OK, because they feel like they need to make things fast, but it's rare that the overhead is actually relevant.

12_throw_away 3y ago
Yes! Thank you! Dunno what it is about Rust that makes everyone forget what premature optimization is the root of all of.
- bombela 3y ago
  The zero cost abstraction is so tantalizingly close enough to reach! I tell everybody to .clone() and (a)rc away and optimize later. But I often struggle to do that myself ;)
int_19h 3y ago
If it's syntactically messy, though, it's not really the easy path. Ergonomics matter just as much as semantics. I do think that a superset of Rust that provided first-class native syntax for ARC would be much more popular.