Skip to content

Remove documentation references to garbage collection #13987

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
steveklabnik opened this issue May 6, 2014 · 6 comments
Closed

Remove documentation references to garbage collection #13987

steveklabnik opened this issue May 6, 2014 · 6 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@steveklabnik
Copy link
Member

Rust has never actually had a garbage collector, but we lied about it for years. Time to come clean. I'd like to give all the docs a once-over, and remove all references to garbage collection, except for Gc<T>, obviously.

For example, the lifetimes tutorial: http://static.rust-lang.org/doc/0.10/guide-lifetimes.html

@steveklabnik
Copy link
Member Author

I would tag this 'E-Easy' and "docs" if I could tag things. :)

@alan-andrade
Copy link
Contributor

I'm on this

@alan-andrade
Copy link
Contributor

Ok, here is my final version.

#14387

bors added a commit that referenced this issue May 28, 2014
… r=brson

My main goals were:
- be clear when we talk about "references" and "pointers"
- remove Managed boxes completely and the concept of GC.

#13987
@steveklabnik
Copy link
Member Author

I think this is largely good to go. I'll be keeping a future eye out for it.

@geraldstanje
Copy link

i heard a presentation about rust talking about an optimal gc...is this on ice now? http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Panel-Systems-Programming-Languages-in-2014-and-Beyond

@steveklabnik
Copy link
Member Author

There never was a GC, we just said there was. It was a reference count with cycle detection. The plan was to eventually turn it into a GC, but instead, it's just being removed.

bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 28, 2025
Using `Vec::extend(std::iter::repeat_n(item, N))` allows to use the more
natural number of elements to add `N`, as is probably done in the
original loop, instead of computing the difference between the existing
number of elements and the wanted one.

Before MSRV 1.82, the older suggestion to use `Vec::resize()` is still
issued.

Inspired by rust-lang#6156 (which predates `repeat_n()`).

changelog: [`same_item_push`]: recommend using `Vec::extend()` to extend
a vector
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

4 participants