Skip to content

Confusing docs: Command::output claims to "capture" stdin #44929

@crumblingstatue

Description

@crumblingstatue
Contributor

By default, stdin, stdout and stderr are captured (and used to provide the resulting output).

"capture" makes it sound like the data is stored somewhere for later inspection. There is no stdin field in process::Output.

I did some looking into the implementation, and to me it seems that the child's stdin is simply closed before waiting. @talchas on IRC told me that it's made to be Stdio::null().

In any case, this should be clarified.

cc @steveklabnik

Activity

added
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
on Sep 30, 2017
added
C-enhancementCategory: An issue proposing an enhancement or a PR with one.
on Oct 1, 2017
added a commit that references this issue on Nov 23, 2017
2178e3a
frewsxcv

frewsxcv commented on Nov 23, 2017

@frewsxcv
Member

Opened a pull request for this: #46220

added a commit that references this issue on Nov 23, 2017
e6968df
added a commit that references this issue on Nov 26, 2017
1be38e0
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-enhancementCategory: An issue proposing an enhancement or a PR with one.P-mediumMedium priority

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @steveklabnik@frewsxcv@TimNN@crumblingstatue@GuillaumeGomez

        Issue actions

          Confusing docs: Command::output claims to "capture" stdin · Issue #44929 · rust-lang/rust