rust/src/libstd/sys/cloudabi/time.rs, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2020-07-28T00:51:13+00:00mv std libs to library/2020-07-28T00:51:13+00:00markmarkm@cs.wisc.edu2020-06-12T02:31:49+00:00urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0Format libstd/sys with rustfmt2019-11-30T02:37:58+00:00David Tolnaydtolnay@gmail.com2019-11-27T18:28:39+00:00urn:sha1:c34fbfaad38cf5829ef5cfe780dc9d58480adeaa
This commit applies rustfmt with rust-lang/rust's default settings to
files in src/libstd/sys *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/sys -name '*.rs' \
| xargs rustfmt --edition=2018 --unstable-features --skip-children
$ rg libstd/sys outstanding_files | xargs git checkout --
Repeating this process several months apart should get us coverage of
most of the rest of the files.
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
Use raw pointers in std::sys::cloudabi when passing MaybeUninit values2019-07-23T17:51:28+00:00Nathannathan.whitaker01@gmail.com2019-07-23T17:51:28+00:00urn:sha1:b70f21726238d73e671179ca6fe54ec228c75870Cleanup std::sys::cloudabi2019-07-23T17:49:37+00:00Nathannathan.whitaker01@gmail.com2019-07-23T14:20:33+00:00urn:sha1:0ac6afafa61044831c6e019e8aee46ecc7243d90Remove uses of mem::uninitialized in std::sys::cloudabi2019-07-23T00:42:08+00:00Nathannathan.whitaker01@gmail.com2019-07-22T21:17:37+00:00urn:sha1:e1e0df8a49d8c172261be1d71e33632200629cce
Usages still appear in cloudabi tests and in the reentrant mutex implementationUpdate sys::time impls to have checked_sub_instant2019-03-22T22:56:40+00:00Linus Färnstrandfaern@faern.net2019-03-22T21:14:35+00:00urn:sha1:1ccad16231f58b09f127e679d54162acbc2f0daelibstd => 20182019-02-27T19:06:15+00:00Taiki Endote316e89@gmail.com2019-02-10T19:23:21+00:00urn:sha1:93b6d9e086c6910118a57e4332c9448ab550931fstd: Force `Instant::now()` to be monotonic2019-01-07T16:00:47+00:00Alex Crichtonalex@alexcrichton.com2018-12-19T18:29:23+00:00urn:sha1:255a3f3e183150e30d411628d5996bd3a183bd6f
This commit is an attempt to force `Instant::now` to be monotonic
through any means possible. We tried relying on OS/hardware/clock
implementations, but those seem buggy enough that we can't rely on them
in practice. This commit implements the same hammer Firefox recently
implemented (noted in #56612) which is to just keep whatever the lastest
`Instant::now()` return value was in memory, returning that instead of
the OS looks like it's moving backwards.
Closes #48514
Closes #49281
cc #51648
cc #56560
Closes #56612
Closes #56940
Remove licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718cFix dur2intervals import on cloudabi2018-12-13T17:49:54+00:00Linus Färnstrandfaern@faern.net2018-12-13T14:24:50+00:00urn:sha1:9e5e89a0d37b06e4f6915809b6a21409727acdc1