https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.34.0 2019-02-25T20:24:10+00:00 2019-02-25T20:24:10+00:00 bors bors@rust-lang.org 2019-02-25T20:24:10+00:00 urn:sha1:00aae71f503b1ab592f48de47dd30912f3858748 Stabilize TryFrom and TryInto with a convert::Infallible empty enum This is the plan proposed in https://github.com/rust-lang/rust/issues/33417#issuecomment-423073898 2019-02-23T08:25:12+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-02-23T08:25:12+00:00 urn:sha1:f19bec89d784dfa8b5a372b4cefeb83c5196a3ef RangeInclusive internal iteration performance improvement. Specialize `Iterator::try_fold` and `DoubleEndedIterator::try_rfold` to improve code generation in all internal iteration scenarios. This changes brings the performance of internal iteration with `RangeInclusive` on par with the performance of iteration with `Range`: - Single conditional jump in hot loop, - Unrolling and vectorization, - And even Closed Form substitution. Unfortunately, it only applies to internal iteration. Despite various attempts at stream-lining the implementation of `next` and `next_back`, LLVM has stubbornly refused to optimize external iteration appropriately, leaving me with a choice between: - The current implementation, for which Closed Form substitution is performed, but which uses 2 conditional jumps in the hot loop when optimization fail. - An implementation using a `is_done` boolean, which uses 1 conditional jump in the hot loop when optimization fail, allowing unrolling and vectorization, but for which Closed Form substitution fails. In the absence of any conclusive evidence as to which usecase matters most, and with no assurance that the lack of Closed Form substitution is not indicative of other optimizations being foiled, there is no way to pick one implementation over the other, and thus I defer to the statu quo as far as `next` and `next_back` are concerned. 2019-02-20T03:59:26+00:00 kennytm kennytm@gmail.com 2019-02-19T17:13:49+00:00 urn:sha1:8ca56e1e0226cb70081df497ffd555f5bb4ace52 Stabilize iter::successors and iter::from_fn FCP: https://github.com/rust-lang/rust/issues/58045#issuecomment-464674773, https://github.com/rust-lang/rust/issues/55977#issuecomment-463964234 2019-02-19T13:10:07+00:00 Simon Sapin simon.sapin@exyr.org 2019-02-19T13:10:07+00:00 urn:sha1:3906cb9187d92a39435086de113ab67b6dd9ba43 FCP: https://github.com/rust-lang/rust/issues/55977#issuecomment-463964234 2019-02-17T12:04:48+00:00 Konrad Borowski konrad@borowski.pw 2019-02-17T12:04:48+00:00 urn:sha1:0cf1a912e37e6b3be747deb18a521c1d3657afc0 2019-02-17T11:58:48+00:00 Konrad Borowski konrad@borowski.pw 2019-02-17T11:58:48+00:00 urn:sha1:3281e621885e45f0b253acb257a22f12d0623fe8 2019-02-13T17:21:13+00:00 Ralf Jung post@ralfj.de 2019-02-13T16:18:47+00:00 urn:sha1:4c1a1c38305d72fc564f554ae980105d74331108 2019-02-13T17:21:13+00:00 Ralf Jung post@ralfj.de 2019-02-13T12:25:46+00:00 urn:sha1:e24af6c2b32679e398b2a2b1bc81ab9c258d8765 2019-02-13T17:21:13+00:00 Ralf Jung post@ralfj.de 2019-02-09T15:19:21+00:00 urn:sha1:72be9a607bd127cdd5cdb3f1f53af725f4eeef98 2019-02-13T17:00:18+00:00 Simon Sapin simon.sapin@exyr.org 2019-02-08T14:00:47+00:00 urn:sha1:c80a8f51dcdc90dd8a5234f3bef6160814eee5df