Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement some garbage collector #11778

Closed
brson opened this issue Jan 24, 2014 · 6 comments
Closed

Implement some garbage collector #11778

brson opened this issue Jan 24, 2014 · 6 comments
Labels
P-medium Medium priority

Comments

@brson
Copy link
Contributor

brson commented Jan 24, 2014

I don't see any issue about just getting garbage collection working, which it increasingly looks like we want to have done for 1.0. Nominating.
@flaper87
Copy link
Contributor

related to #11399

@thestinger thestinger mentioned this issue Jan 25, 2014
Closed
@huonw
Copy link
Member

huonw commented Jan 25, 2014

The near-identical #2997 was accepted for P-low.

@pnkfelix
Copy link
Member

Accepted for 1.0, assigning P-backcompat-libs (but we may revisit priority assignment later...)

@brson brson mentioned this issue Feb 5, 2014
Closed
@brson
Copy link
Contributor Author

brson commented Jun 19, 2014

Nominating for removal from milestone. Does not seem possible.

@emberian emberian modified the milestone: 1.0 Jun 26, 2014
@pnkfelix
Copy link
Member

We should create a separate ticket for ensuring that our allocator design, whenever it is created, properly supports a reasonable form of garbage collection.

Taking off the 1.0 milestone and removing the P-backcompat-lib; reassigning P-high.

@pnkfelix pnkfelix modified the milestone: 1.0 Jun 26, 2014
@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#679

@steveklabnik steveklabnik mentioned this issue Jan 21, 2015
Closed
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 16, 2023
@bors
Auto merge of rust-lang#11778 - granddaifuku:fix/reduce-indexing-manu…
ca8f33e 
…al_memcpy-when-array-length-is-equal-to-range, r=blyxyas

fix: [manual_memcpy] reduce indexing suggestions when array length is equal to loop range

fixes: rust-lang#11689

This PR improves `manual_memcpy` suggestions by reducing unnecessary indexing.

For example,
```rust
let src = [0, 1, 2, 3, 4];
let mut dest = [0; 4];
for i in 0..4 {
    dest[i] = src[i];
{
```
Clippy suggests `dest[..4].copy_from_slice(&src[..4]);`.
I reduced this suggestion as `dest.copy_from_slice(&src[..4]);`. (Removed needless indexing.)

changelog: [`manual_memcpy`]: Reduce indexing suggestions when array length is equal to loop range
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P-medium Medium priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@flaper87 @steveklabnik @brson @pnkfelix @emberian @huonw @thestinger