Rust

6137 readers

9 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago

MODERATORS

[email protected]

236

Productivity of Rust teams at Google (programming.dev)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]

124 comments fedilink hide all child comments

Slide with text: “Rust teams at Google are as productive as ones using Go, and more than twice as productive as teams using C++.”

In small print it says the data is collected over 2022 and 2023.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 13 points 9 months ago* (last edited 9 months ago) (2 children)

instead of messing with lifetimes, borrow checker and other stuff I actually don’t care about at all

There's nothing wrong with putting Rc<_> or Rc<RefCell<_>> around data if you don't want to fight the borrow checker or think about lifetimes even if you know it can be written without.

[–] [email protected] 4 points 9 months ago

Or even just clone. Depending on use case the performance cost would be negligible.

[–] [email protected] 4 points 9 months ago (1 children)

There's nothing wrong with putting Rc<> or Rc<RefCell<>> around data

It's mainly the visual pollution that bothers me. Wrapping everything in the reference counting smart pointers just because you can't be bothered dealing with the borrow checker seems like an antipattern

[–] [email protected] 3 points 9 months ago

I don't know why so many recommend Rc or Arc as a catchall. 90% of the time if you want to avoid the borrow checker then a clone or copy is good enough.