Uh oh!
There was an error while loading. Please reload this page.
Safety docs about process::Child going out of scope - #31327
Merged
Conversation
There is no `Drop` implemented for `Child`, so if it goes out of scope in Rust-land and gets deallocated, the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually use `kill`, `wait`, or `wait_with_output`. Fixesrust-lang#31289.
Contributor
There was a problem hiding this comment.
AFAIK the "Safety" heading is for memory safety and memory safety only. Also AFAIK a child process terminating later than expected is not a memory safety hazard. If I'm correct about both things, this heading should be renamed.
ContributorAuthor
There was a problem hiding this comment.
@rkruppe: Was wondering about that myself. Any suggestions?
Member
There was a problem hiding this comment.
# Note is usually used for this kind of thing I believe.
dirkforce-pushed
the
dirk/process-child-safety-docs
branch
from
February 1, 2016 04:51
6c730da to
7683922Comparesteveklabnik
commented
Feb 1, 2016
Contributor
re-queueing travis. The structure and format look right to me, but r? @alexcrichton because I don't know enough about the accuracy here. |
alexcrichton
commented
Feb 1, 2016
Member
steveklabnik added a commit
to steveklabnik/rust
that referenced
this pull request
Feb 1, 2016
…, r=alexcrichton `Drop` is not implemented for `Child`, so if it goes out of scope in Rust-land and gets deallocated the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually use `kill`, `wait`, or `wait_with_output`. Fixesrust-lang#31289. r? @steveklabnik
steveklabnik added a commit
to steveklabnik/rust
that referenced
this pull request
Feb 2, 2016
…, r=alexcrichton `Drop` is not implemented for `Child`, so if it goes out of scope in Rust-land and gets deallocated the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually use `kill`, `wait`, or `wait_with_output`. Fixesrust-lang#31289. r? @steveklabnik
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dropis not implemented forChild, so if it goes out of scope in Rust-land and gets deallocated the child process will continue to exist and execute. If users want a guarantee that the process has finished running and exited they must manually usekill,wait, orwait_with_output.Fixes#31289.
r? @steveklabnik