Repository navigation
API Docs: process #29370
Description
Activity
This API really could use a better documentation. To list all failure cases of several functions would be great :)
- added 5 commits that reference this issue
on May 5, 2016 - addedE-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
on Mar 8, 2017 I am happy to mentor anyone who wants to tackle this issue.
- addedA-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Documentation for any part of the project, including the compiler, standard library, and tools
on Mar 10, 2017 52 remaining items
@steveklabnik the two abort check boxes should be ticked off now that #44905 was merged
- added a commit that references this issue
on Oct 8, 2017 I'd like to help improve the module docs.
@Technius that'd be great! Let me know if you need any help!
The
ExitStatus,Output, andStdiocan be checked off now, as well as the default behaviour ofstdin/stdout/stderr.The
Commandbox can possibly also be checked off (at least it looks good to me, not sure what other detail is needed).All that's left (I think) is module level documentation, and an explanation of how stdio works in different Windows subsystems.
- added a commit that references this issue
on Oct 29, 2017 I'm giving this issue a close. Thank you to everyone who's pitched in on these docs over the last few years. If there's still improvements to do here, please open a new issue, one per thing. Thanks!
Part of #29329
http://doc.rust-lang.org/std/process/
Here's what needs to be done to close out this issue:
abortneeds an example, preferably showing off its destuctor behavior. (some elaboration here, and a first PR here)abortshould also talk about its relationship withpanic!, specifically, unwinding vs aborting panics.aborthas a bug:The [abort] function terminates the process, the[]s need to be dropped.ChildtheNoteshouldn't be one, and should come before the examples.ChildStderrshould have its second sentence as not a summary, needs some newlines.ChildStdinhas the same issue.ChildStdouthas the same issue.Commandis good but many of its methods could use more elaboration in their docs. See below for some details.ExitStatusshould link tostatus, and itscodemethod needs an example.Outputshould link tooutput.Stdioshould link tostdioand needs expanded explanations and examples.exitneeds some examples to show its behavior. An example of how people use this inmainwould be fantastic too.With regards to
Command, @frewsxcv brought up in #40983 thatstdin,stdout, andstderrshould specify what the default behavior is if they aren't explicitly called.And @retep998 mentions