https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=beta 2020-07-28T00:51:13+00:00 2020-07-28T00:51:13+00:00 mark markm@cs.wisc.edu 2020-06-12T02:31:49+00:00 urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0 2020-07-23T07:42:01+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-23T07:42:01+00:00 urn:sha1:9be109910713660e666f83ebdc6a6e717391e647 libstd/libcore: fix various typos 2020-07-21T06:55:17+00:00 bors bors@rust-lang.org 2020-07-21T06:55:17+00:00 urn:sha1:8ad7bc3f428300aee6764f6e23527e19eb235e81 Add `RawFd` to WASI's `std::os::wasi::prelude`. Add `RawFd` to WASI's `std::os::wasi::prelude`, making it consistent with all other platforms which also have `AsRawFd`, `FromRawFd`, and `IntoRawFd` in their respective preludes. 2020-07-15T16:57:05+00:00 Eric Huss eric@huss.org 2020-06-01T01:09:25+00:00 urn:sha1:6e9a1de0d146734e51cc7e761b288e9b9b138d4f 2020-07-14T20:19:28+00:00 Manish Goregaokar manishsmail@gmail.com 2020-07-14T20:19:28+00:00 urn:sha1:fadd91c630bb4cf606f7ef3ec68d7b6cbcb363b5 Slight reorganization of sys/(fast_)thread_local I was long confused by the `thread_local` and `fast_thread_local` modules in the `sys(_common)` part of libstd. The names make it *sound* like `fast_thread_local` is just a faster version of `thread_local`, but really these are totally different APIs: one provides thread-local "keys", which are non-addressable pointer-sized pieces of local storage with an associated destructor; the other (the "fast" one) provides just a destructor. So I propose we rename `fast_thread_local` to `thread_local_dtor`, and `thread_local` to `thread_local_key`. That's what this PR does. 2020-07-12T09:46:42+00:00 Ralf Jung post@ralfj.de 2020-07-12T09:45:04+00:00 urn:sha1:7dc388654d6ef038065db23340e8eff7a567e5b4 2020-07-09T14:57:11+00:00 Andy Russell arussell123@gmail.com 2020-07-08T00:48:15+00:00 urn:sha1:133e91da627a42218721caf2083c3f309e1b0dcc 2020-07-07T23:04:52+00:00 Dan Gohman sunfish@mozilla.com 2020-07-07T22:56:07+00:00 urn:sha1:58fc61b79cd15fdafad6e15991553f5c33422ade Rename the existing read_at/write_at to read_vectored_at/write_vectored_at, for consistency with libstd's read_vectored/write_vectored. And, introduce new read_at/write_at functions which take a single buffer, similar to all other targets which provide these functions, so this will make it easier for applications to share code between WASI and other targets. Note that WASI's FileExt is currently unstable. 2020-07-07T23:04:52+00:00 Dan Gohman sunfish@mozilla.com 2020-07-03T23:20:37+00:00 urn:sha1:653c0912628382388ceb8a3cf29e88dad35b98ac This adds `read_exact_at` and `write_all_at` to WASI's `FileExt`, similar to the Unix versions of the same names. 2020-07-05T23:02:34+00:00 Dan Gohman sunfish@mozilla.com 2020-07-03T22:56:50+00:00 urn:sha1:83bd3d3975bd56e0bd959b5df8129e4ee21aeca3 Add `RawFd` to WASI's `std::os::wasi::prelude`, making it consistent with all other platforms which also have `AsRawFd`, `FromRawFd`, and `IntoRawFd` in their respective preludes.