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.

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

The Guide to the Rust Runtime needs to be updated #17923

Closed
aochagavia opened this issue Oct 10, 2014 · 3 comments
Closed

The Guide to the Rust Runtime needs to be updated #17923

aochagavia opened this issue Oct 10, 2014 · 3 comments
Assignees
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@aochagavia
Copy link
Contributor

As a consequence of #17325 (removing of libgreen), the Guide to the Rust Runtime needs to be updated. Currently, there are many references to libgreen thar aren't valid anymore.

@aochagavia
Copy link
Contributor Author

cc @steveklabnik

@thestinger
Copy link
Contributor

It needs removal, not a rewrite. None of the information is going to be relevant once the work is complete and it's not accurate now.

@steveklabnik steveklabnik self-assigned this Oct 10, 2014
@aturon
Copy link
Member

aturon commented Oct 10, 2014

Yes, this guide needs to be dropped completely.

@thestinger thestinger added the E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. label Oct 10, 2014
bors added a commit that referenced this issue Oct 11, 2014
…crichton

Now that libgreen is gone, this is all wrong.

Fixes #17923
bors added a commit that referenced this issue Oct 11, 2014
…crichton

Now that libgreen is gone, this is all wrong.

Fixes #17923
lnicola pushed a commit to lnicola/rust that referenced this issue Oct 8, 2024
…art-debug, r=Veykril

Building before a debugging session was restarted

# Background
Resolves rust-lang#17901. It adds support for rebuilding after debugging a test was restarted. This means the test doesn't have to be aborted and manually re-ran again.

# How this is tested
First, all the Visual Studio Code extensions are loaded into an Extension Host window. Then, a sample test like below was ran and restarted to see if it was correctly rebuild.

```rust
#[test]
fn test_x() {
    assert_eq!("1.1.1", "1.1.0");
}
```
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

Successfully merging a pull request may close this issue.

4 participants