Rust 1.53

I love the `|` matching anywhere in a pattern. That will certainly cut down on a <i>lot</i> of code and improve readability.

Should one learn Rust, lets say after 3-4 years, i.e by mid 2020s, once it becomes more mainstream? The syntax of Rust is a mix of OCaml&#x2F;C++ and I feel some of the concepts are very esoteric for a normal enterprise Java&#x2F;C#&#x2F;JS&#x2F;Python developer, so it takes a lot of cognitive overload to master it. So is it worth learning now or later?

At last, I&#x27;m able to pass bona fide stack-allocated iterators of a few elements into things. I&#x27;m very happy with this newly gained array neatness.

&gt; Identifiers can now contain non-ascii characters. All valid identifier characters in Unicode as defined in UAX #31 can now be used. That includes characters from many different scripts and languages, but does not include emoji.<p>Don&#x27;t despair fellow emoji devs, our time will come soon enough.

I just recompiled rustc on my Linux From Scratch desktop. I guess I should have timed it, but it sure felt a lot faster. Finished when I wasn&#x27;t even paying attention.<p>Went from 9 failed tests on 1.52.1 to 13 on 1.53.0.<p>I&#x27;m not expecting Firefox to compile, but that&#x27;s entirely on Mozilla.

I love the non-ascii character support although for me as an English speaker I wouldn&#x27;t use it, but I&#x27;m sure there many Asian teams that would appreciate these changes<p><pre><code> struct 人 { 名字: String, }</code></pre>

Sweet, cmp::min_by_key and cmp::max_by_key have finally been stabilized. Was sorely missing this little convenience in Rust, as it helps express a particular idea more clearly and succinctly.<p>Also the improvement to compile times on macOS due to the change in how debug info is stored is a nice productivity boost.

I&#x27;m a little OT (sorry), but I am wondering if is there a way to learn Rust while keeping up with the changes made from last edition (Rust 2018, which is 1.31)?