Rust

6005 readers

3 users here now

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

Wormhole

!performance@programming.dev

Credits

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

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

242

Productivity of Rust teams at Google (programming.dev)

submitted 7 months ago* (last edited 7 months ago) by arendjr@programming.dev to c/rust@programming.dev

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

[–] tatterdemalion@programming.dev 3 points 7 months ago* (last edited 7 months ago) (1 children)

Cyclic reference-counted pointers are the most probable way to accidentally leak memory. But it's a pretty well known anti-pattern that is not hard to avoid.

[–] lolcatnip@reddthat.com 3 points 7 months ago

Yeah, I didn't think of that case, because any time I use ref counting, cyclic references are at the from of my mind.