<story><title>Rust 1.25 released</title><url>https://blog.rust-lang.org/2018/03/29/Rust-1.25.html</url></story><parent_chain><item><author>kibwen</author><text>The big thing in this one is the LLVM upgrade, which has been a &lt;i&gt;long&lt;/i&gt; time coming. :) We actually skipped LLVM 5 entirely due to some issues with emscripten. It&amp;#x27;ll be great to finally be able to experiment with LLD.&lt;p&gt;Looking forward, the next two releases, 1.26 and 1.27, are going to have some major features that we&amp;#x27;ve been working on for a long, long time, such as &amp;quot;impl trait&amp;quot; (which should allow for improved performance, simpler syntax for the typical use of generics, and greatly improve error messages for extensive use of generics), more ergonomic matching when dealing with references, 128-bit integers, stable SIMD library support, and others. This whole year is going to see the continued stabilization of the ergonomics intiatives from last year, so stay tuned for lots of welcome tweaks to make Rust easier to write and read. :)&lt;p&gt;(I should also mention that this release happened live from the Rust All-Hands happening in Berlin, which has been a massively productive time so far; keep an eye out for the eventual workweek recap which will hopefully enumerate the tons of improvements (e.g. reducing Rust binary sizes by 10%) and future initiatives (e.g. forming an official Verification Team) that have happened this week.)</text></item></parent_chain><comment><author>pedrocr</author><text>&amp;gt;The big thing in this one is the LLVM upgrade, which has been a long time coming.&lt;p&gt;This is great news. I just ran my usual benchmark and it seems a performance regression has been fixed and some performance added over that. I&amp;#x27;m measuring the speed of loading a Sony A77 raw file in rawloader[1]. That includes TIFF parsing and then a tight loop that processes every pixel. Here&amp;#x27;s the version history:&lt;p&gt;1.17 - 95ms&lt;p&gt;1.18 - 80ms (-16%)&lt;p&gt;1.19 - 79ms (-16%)&lt;p&gt;1.20 - 80ms (-16%)&lt;p&gt;1.21 - 79ms (-17%)&lt;p&gt;1.22 - 79ms (-17%)&lt;p&gt;1.23 - 79ms (-17%)&lt;p&gt;1.24 - 84ms (-12%)&lt;p&gt;1.25 - 74ms (-22%)&lt;p&gt;I believe the jump in 1.18 was LLVM 4.0 and now LLVM 6.0 is giving me a new performance jump. No idea what happened in 1.24 though but it seems to be fixed now.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pedrocr&amp;#x2F;rawloader&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;pedrocr&amp;#x2F;rawloader&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Rust 1.25 released</title><url>https://blog.rust-lang.org/2018/03/29/Rust-1.25.html</url></story><parent_chain><item><author>kibwen</author><text>The big thing in this one is the LLVM upgrade, which has been a &lt;i&gt;long&lt;/i&gt; time coming. :) We actually skipped LLVM 5 entirely due to some issues with emscripten. It&amp;#x27;ll be great to finally be able to experiment with LLD.&lt;p&gt;Looking forward, the next two releases, 1.26 and 1.27, are going to have some major features that we&amp;#x27;ve been working on for a long, long time, such as &amp;quot;impl trait&amp;quot; (which should allow for improved performance, simpler syntax for the typical use of generics, and greatly improve error messages for extensive use of generics), more ergonomic matching when dealing with references, 128-bit integers, stable SIMD library support, and others. This whole year is going to see the continued stabilization of the ergonomics intiatives from last year, so stay tuned for lots of welcome tweaks to make Rust easier to write and read. :)&lt;p&gt;(I should also mention that this release happened live from the Rust All-Hands happening in Berlin, which has been a massively productive time so far; keep an eye out for the eventual workweek recap which will hopefully enumerate the tons of improvements (e.g. reducing Rust binary sizes by 10%) and future initiatives (e.g. forming an official Verification Team) that have happened this week.)</text></item></parent_chain><comment><author>simias</author><text>&amp;gt;stable SIMD library support&lt;p&gt;Oh, that&amp;#x27;s a huge one for me and I didn&amp;#x27;t even know it was in the pipeline, very happy to hear that. Now I&amp;#x27;ll have to complain about lack of stable inline ASM support instead!</text></comment>