rust/src/libstd/process.rs, branch try

mv std libs to library/

2020-07-28T00:51:13+00:00

Implement `Sync` for `process::Command on unix and vxworks

2020-05-22T16:33:12+00:00

abort_internal is safe

2020-05-17T21:38:31+00:00

Update name

2020-04-26T11:24:16+00:00

Add Read/Write::can_read/write_vectored

2020-04-26T11:23:39+00:00

When working with an arbitrary reader or writer, code that uses vectored operations may end up being slower than code that copies into a single buffer when the underlying reader or writer doesn't actually support vectored operations. These new methods allow you to ask the reader or witer up front if vectored operations are efficiently supported. Currently, you have to use some heuristics to guess by e.g. checking if the read or write only accessed the first buffer. Hyper is one concrete example of a library that has to do this dynamically: https://github.com/hyperium/hyper/blob/0eaf304644a396895a4ce1f0146e596640bb666a/src/proto/h1/io.rs#L582-L594

Format libstd with rustfmt

2019-11-30T02:43:27+00:00

This commit applies rustfmt with rust-lang/rust's default settings to files in src/libstd *that are not involved in any currently open PR* to minimize merge conflicts. THe list of files involved in open PRs was determined by querying GitHub's GraphQL API with this script: https://gist.github.com/dtolnay/aa9c34993dc051a4f344d1b10e4487e8 With the list of files from the script in outstanding_files, the relevant commands were: $ find src/libstd -name '*.rs' \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ rg libstd outstanding_files | xargs git checkout -- Repeating this process several months apart should get us coverage of most of the rest of libstd. To confirm no funny business: $ git checkout $THIS_COMMIT^ $ git show --pretty= --name-only $THIS_COMMIT \ | xargs rustfmt --edition=2018 --unstable-features --skip-children $ git diff $THIS_COMMIT # there should be no difference

Ignore these tests ,since the called commands doesn't exist in VxWorks

2019-11-07T03:51:25+00:00

Remove leading :: from paths in doc examples

2019-10-20T18:13:47+00:00

Rollup merge of #64294 - wchargin:wchargin-stdio-piped-docs, r=Dylan-DPC

2019-09-22T22:36:33+00:00

Fix `Stdio::piped` example code and lint Summary: Invoking `rev` does not add a trailing newline when none is present in the input (at least on my Debian). Nearby examples use `echo` rather than `rev`, which probably explains the source of the discrepancy. Also, a `mut` qualifier is unused. Test Plan: Copy the code block into with a `fn main` wrapper, and run it. Note that it compiles and runs cleanly; prior to this commit, it would emit an `unused_mut` warning and then panic. wchargin-branch: stdio-piped-docs

Remove unnecessary `mut` in doc example

2019-09-19T11:36:10+00:00