https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2018-01-15T06:09:53+00:00 2018-01-15T06:09:53+00:00 Fenrir fenrirwolf@gmail.com 2018-01-15T06:07:51+00:00 urn:sha1:1482afbbedfbbd6920b8cf05bd23ba30a36630ce 2017-11-09T04:41:17+00:00 Alex Crichton alex@alexcrichton.com 2017-11-01T19:32:13+00:00 urn:sha1:6bc8f164b09b9994e6a2d4c4ca60d7d36c09d3fe This commit removes the `rand` crate from the standard library facade as well as the `__rand` module in the standard library. Neither of these were used in any meaningful way in the standard library itself. The only need for randomness in libstd is to initialize the thread-local keys of a `HashMap`, and that unconditionally used `OsRng` defined in the standard library anyway. The cruft of the `rand` crate and the extra `rand` support in the standard library makes libstd slightly more difficult to port to new platforms, namely WebAssembly which doesn't have any randomness at all (without interfacing with JS). The purpose of this commit is to clarify and streamline randomness in libstd, focusing on how it's only required in one location, hashmap seeds. Note that the `rand` crate out of tree has almost always been a drop-in replacement for the `rand` crate in-tree, so any usage (accidental or purposeful) of the crate in-tree should switch to the `rand` crate on crates.io. This then also has the further benefit of avoiding duplication (mostly) between the two crates! 2017-06-16T18:40:40+00:00 est31 MTest31@outlook.com 2017-06-16T17:58:37+00:00 urn:sha1:c6afde6c46d167c9c75389b887f1d2498aeef3e4 This commit * Refactors the collect_lib_features function to work in a non-checking mode (no bad pointer needed, and list of lang features). * Introduces checking whether unstable/stable tags for a given feature have inconsistent tracking issues. * Fixes such inconsistencies throughout the codebase. 2017-03-12T18:59:04+00:00 Corey Farwell coreyf@rwell.org 2017-03-12T18:13:35+00:00 urn:sha1:97a1b6a055d69cf21faa9773133725bdfddc5196 As of last year with version 'Sierra', the Mac operating system is now called 'macOS'. 2016-12-18T22:55:14+00:00 Corey Farwell coreyf@rwell.org 2016-11-25T18:21:49+00:00 urn:sha1:86fc63e62ddc0a271210b8cc7cc2a6de6874b8f8 Part of https://github.com/rust-lang/rust/issues/31869. Also turn on the `missing_debug_implementations` lint at the crate level. 2016-10-31T22:51:40+00:00 iirelu anna@bawk.space 2016-10-29T21:54:04+00:00 urn:sha1:e593c3b89343a98bdcc76ce9f5869ff18882dfff Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-09-30T21:02:48+00:00 Brian Anderson banderson@mozilla.com 2016-09-07T05:34:15+00:00 urn:sha1:9c4a01ee9eea6fc50252f08afbf98a91270e9d5e 2016-02-18T00:21:32+00:00 Sean McArthur sean.monstar@gmail.com 2016-02-17T21:56:16+00:00 urn:sha1:34dfc3991db26a363657f0bd56db1669032468b3 2016-02-11T19:12:32+00:00 Alex Crichton alex@alexcrichton.com 2016-01-21T23:36:25+00:00 urn:sha1:eac0a8bc3070e45047fff57e7b024a059289a36d Have all Cargo-built crates pass `--cfg cargobuild` and then add appropriate `#[cfg]` definitions to all crates to avoid linking anything if this is passed. This should help allow libstd to compile with both the makefiles and with Cargo. 2016-02-02T04:39:07+00:00 Alex Crichton alex@alexcrichton.com 2016-01-30T21:27:00+00:00 urn:sha1:8f803c202681fa137fca691df999ac3f335d29c1 Currently the `mipsel-unknown-linux-gnu` target doesn't actually set the `target_arch` value to `mipsel` but it rather uses `mips`. Alternatively the `powerpc64le` target does indeed set the `target_arch` as `powerpc64le`, causing a bit of inconsistency between theset two. As these are just the same instance of one instruction set, let's use `target_endian` to switch between them and only set the `target_arch` as one value. This should cut down on the number of `#[cfg]` annotations necessary and all around be a little more ergonomic.