rust/src/libstd/sys/wasm, branch perf-tmp https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp 2020-07-28T00:51:13+00:00 mv std libs to library/ 2020-07-28T00:51:13+00:00 mark markm@cs.wisc.edu 2020-06-12T02:31:49+00:00 urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0 Introduce restricted-std feature. 2020-07-15T16:57:05+00:00 Eric Huss eric@huss.org 2020-06-01T01:09:25+00:00 urn:sha1:6e9a1de0d146734e51cc7e761b288e9b9b138d4f adjust remaining targets 2020-07-12T09:46:42+00:00 Ralf Jung post@ralfj.de 2020-07-12T09:45:04+00:00 urn:sha1:7dc388654d6ef038065db23340e8eff7a567e5b4 Migrate to numeric associated consts 2020-06-10T01:35:47+00:00 Lzu Tao taolzu@gmail.com 2020-06-02T07:59:11+00:00 urn:sha1:fff822fead6249671cbcb090b24bce58fab38de0 abort_internal is safe 2020-05-17T21:38:31+00:00 Ralf Jung post@ralfj.de 2020-05-17T17:37:44+00:00 urn:sha1:2764673dca6badb2ef89450bbdd84b19c317a9c7 fix wasm build 2020-04-26T23:34:14+00:00 Steven Fackler sfackler@gmail.com 2020-04-26T23:34:14+00:00 urn:sha1:b00afb5782c3c9a710f64e5c14f854946847ca65 Update name 2020-04-26T11:24:16+00:00 Steven Fackler sfackler@gmail.com 2020-03-12T01:02:52+00:00 urn:sha1:07443f17d4c2e8135d1cbf415f6bd22eee86b64a Add Read/Write::can_read/write_vectored 2020-04-26T11:23:39+00:00 Steven Fackler sfackler@gmail.com 2020-01-03T19:26:05+00:00 urn:sha1:15262ec6be6fcfc9f27e174a0714d5a62e775fb0 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 Remove stack overflow handler stub for wasm. 2020-04-02T14:15:12+00:00 Vytautas Astrauskas astrauv@amazon.com 2020-04-02T14:15:12+00:00 urn:sha1:ec8275c364493b938357a3615216e3f30c60a443 Rollup merge of #69955 - alexcrichton:stderr-infallible, r=sfackler 2020-03-21T12:06:38+00:00 Dylan DPC dylan.dpc@gmail.com 2020-03-21T12:06:38+00:00 urn:sha1:276b54e9c930c4ff015e1958ad1c640deffd29b2 Fix abort-on-eprintln during process shutdown This commit fixes an issue where if `eprintln!` is used in a TLS destructor it can accidentally cause the process to abort. TLS destructors are executed after `main` returns on the main thread, and at this point we've also deinitialized global `Lazy` values like those which store the `Stderr` and `Stdout` internals. This means that despite handling TLS not being accessible in `eprintln!`, we will fail due to not being able to call `stderr()`. This means that we'll double-panic quickly because panicking also attempt to write to stderr. The fix here is to reimplement the global stderr handle to avoid the need for destruction. This avoids the need for `Lazy` as well as the hidden panic inside of the `stderr` function. Overall this should improve the robustness of printing errors and/or panics in weird situations, since the `stderr` accessor should be infallible in more situations.