Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I did some quick search, not sure if this supports or denies your point:

- 151 instances of "Arc<" in Servo: https://github.com/search?q=repo%3Aservo%2Fservo+Arc%3C&type...

- 5 instances of "Arc<" in AWS SDK for Rust https://github.com/search?q=repo%3Arusoto%2Frusoto%20Arc%3C&...

- 0 instances for "Arc<" in LOC https://github.com/search?q=repo%3Acgag%2Floc%20Arc%3C&type=...



- 454 instances of "Rc<" in Servo: https://github.com/search?q=repo%3Aservo%2Fservo+Rc%3C&type=...

- 6 instances of "Rc<" in AWS SDK for Rust: https://github.com/search?q=repo%3Arusoto%2Frusoto+Rc%3C&typ...

- 0 instance for "Rc<" in LOC: https://github.com/search?q=repo%3Acgag%2Floc+Rc%3C&type=cod...

(Disclaimer: I don't know what these repos are except Servo).


Servo has to interact a lot with a JS runtime, and it needs to be done in a thread safe and concurrent manner.

Plus the html processing needs to be Arc as well, so that tracks.


Why would you expect the AWS SDK to have complicated memory management?


I don't? Those were just from a quick search and I didn't want to cherrypick either way.


OK. I was just caught out because you'd expect the AWS SDK to be distinctively simple (at least relative to its size). It's an HTTP API wrapper.


Appreciate the real numbers. Would be interesting to see what percentage of data structures contain Arc, but that's a lot more work.


Don't forget clone()




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: