Skip to content

API Docs: process #29370

Description

@steveklabnik

Part of #29329

http://doc.rust-lang.org/std/process/

Here's what needs to be done to close out this issue:

  • the module docs are okay but could use elaboration.
  • abort needs an example, preferably showing off its destuctor behavior. (some elaboration here, and a first PR here)
  • abort should also talk about its relationship with panic!, specifically, unwinding vs aborting panics.
  • abort has a bug: The [abort] function terminates the process, the []s need to be dropped.
  • Child the Note shouldn't be one, and should come before the examples.
  • ChildStderr should have its second sentence as not a summary, needs some newlines.
  • ChildStdin has the same issue.
  • ChildStdout has the same issue.
  • Command is good but many of its methods could use more elaboration in their docs. See below for some details.
  • ExitStatus should link to status, and its code method needs an example.
  • Output should link to output.
  • Stdio should link to stdio and needs expanded explanations and examples.
  • exit needs some examples to show its behavior. An example of how people use this in main would be fantastic too.

With regards to Command, @frewsxcv brought up in #40983 that

  • stdin, stdout, and stderr should specify what the default behavior is if they aren't explicitly called.

And @retep998 mentions

Note that the default behavior depends on whether the child process is using the console subsystem or windows subsystem. Console subsystem apps will inherit your stdout/stdin/stderr while windows subsystem apps will start with no stdout/stdin/stderr unless you explicitly assign them.

Activity

  1. LukasKalbertodt commented on Jan 30, 2016

    @LukasKalbertodt
    Contributor

    This API really could use a better documentation. To list all failure cases of several functions would be great :)

  2. added 5 commits that reference this issue on May 5, 2016
  3. added a commit that references this issue on May 7, 2016
  4. added 2 commits that reference this issue on May 7, 2016
  5. added
    E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
    on Mar 8, 2017
  6. steveklabnik commented on Mar 8, 2017

    @steveklabnik
    ContributorAuthor

    I am happy to mentor anyone who wants to tackle this issue.

  7. added
    A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
    on Mar 10, 2017
  8. 52 remaining items

  9. mgattozzi commented on Oct 8, 2017

    @mgattozzi
    Contributor

    @steveklabnik the two abort check boxes should be ticked off now that #44905 was merged

  10. Technius commented on Oct 13, 2017

    @Technius
    Contributor

    I'd like to help improve the module docs.

  11. steveklabnik commented on Oct 13, 2017

    @steveklabnik
    ContributorAuthor

    @Technius that'd be great! Let me know if you need any help!

  12. added 3 commits that reference this issue on Oct 14, 2017
  13. mistodon commented on Oct 17, 2017

    @mistodon

    The ExitStatus, Output, and Stdio can be checked off now, as well as the default behaviour of stdin/stdout/stderr.

    The Command box 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.

  14. added a commit that references this issue on Oct 28, 2017
  15. added a commit that references this issue on Oct 29, 2017
  16. steveklabnik commented on Jan 8, 2019

    @steveklabnik
    ContributorAuthor

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCE-help-wantedCall for participation: Help is requested to fix this issue.E-mediumCall for participation: Medium difficulty. Experience needed to fix: Intermediate.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.P-mediumMedium priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions