about summary refs log tree commit diff
path: root/src/libstd/sys/unix/ext/io.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2019-11-27 12:16:52 +0000
committerbors <bors@rust-lang.org>2019-11-27 12:16:52 +0000
commit04e69e4f4234beb4f12cc76dcc53e2cc4247a9be (patch)
tree148834cf05a0062cc851f578c636241d0bd87b30 /src/libstd/sys/unix/ext/io.rs
parent876a72a251e0d533f776fa9149b3e4daaeea3a61 (diff)
parent166471e7f1f05fe272a4df99c20c1ffc0204a25f (diff)
downloadrust-04e69e4f4234beb4f12cc76dcc53e2cc4247a9be.tar.gz
rust-04e69e4f4234beb4f12cc76dcc53e2cc4247a9be.zip
Auto merge of #66691 - dtolnay:fmt0, r=sfackler
Format libcore with rustfmt

I am interested in whether we can begin cautious incremental progress on #66688 and assess along the way whether we can keep the disruption sufficiently small.

This PR applies rustfmt with default settings to files in src/libcore *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:

```console
$ find src/libcore -name '*.rs' | xargs rustfmt --edition=2018
$ rg libcore outstanding_files | xargs git checkout --
```

Repeating this process several months apart should get us coverage of most of the rest of libcore.
Diffstat (limited to 'src/libstd/sys/unix/ext/io.rs')
0 files changed, 0 insertions, 0 deletions