Cranston's Life - Rust and More Rust

Compiling Rust code using the Rust compiler can be SLOW!

This is a complaint that I have had for some time because even on fast modern hardware there can be a long WAIT when compiling big and complex Rust software.

Brian Anderson writes of this problem in the article The Rust Compilation Model Calamity.

This is the FIRST in a series of posts about this topic and I am so very much looking FORWARD to the rest!

Topics covered include things like the HISTORIC reasons for why and how the Rust compiler became slow, and things like recent work that has been done to IMPROVE the Rust compiler’s compilation time.

This article really makes me UNDERSTAND why the Rust compiler is like it is.

I can’t wait for the NEXT article in this series!

The more I understand the Rust compiler the more I understand the very NATURE of the Rust language itself!

I must STUDY this more.

It is finally HERE!

Rust 1.41.0 has been RELEASED!

New versions of Rust always make me HAPPY!

Rust 1.41.0 has changes like relaxed restrictions when implementing traits, cargo changes, Box and FFI changes, library changes, and MORE!

Rust 1.41.0 is also a BIG DEAL for 32-bit Apple users, because according to the announcement: “Rust 1.41.0 is the last release with the current level of compiler support for 32-bit Apple targets, including the i686-apple-darwin target. Starting from Rust 1.42.0, these targets will be demoted to the lowest support tier.”

I am AMAZED at how Rust keeps getting better and better!

Good job, Rust CONTRIBUTORS!

GOOD JOB!

Testing software is something I consider to be so IMPORTANT.

Rust software is NO exception and the Rust testing, data generation and const asserts article by Ben McDonald is helping me learn more about TESTING Rust code.

This intro to testing Rust software covers IMPORTANT matters like unit tests, integration tests, data generation, assertions, doc tests, useful cargo commands, where to find reputable example tests, and more!

I must STUDY this knowledge more so that I may become a better tester of Rust code.

Rust users will know just how IMPORTANT ownership and the many related concepts are.

Yet acquiring and comprehending this important knowledge is often one of the most CHALLENGING things about learning and using Rust!

Rust ownership is something that I always strive to understand MORE than I already do.

The Rust Ownership by Example article is HELPING me do this.

That article covers TOPICS like assignment, ownership, scoping, reassignment, moves, copying, borrowing, passing by reference, passing by value, string literals, returning borrowed values, lifetimes, mutability, and MARSAW.

While I think I understand the basics, that article has some examples that are making me reconsider the NUANCES of Rust and ownership.

I must STUDY this article and its examples more.

I think that there is always MORE I can learn about ownership, borrowing, and the many other important ideas of Rust.

I have read an article called Bitfields Forever: Why we need a C-compatible Rust Crate by Daniel Kolsoi.

It is yet another article about C2Rust matters that has made me LEARN so much!

The article introduces us to C bitfields and Rust equivalents.

It considers existing crates and code like rust-bitfield, packed_struct, bindgen, and bitvec, and the LESSONS learned from them.

Two new crates were created, c2rust-bitfields and c2rust-bitfields-derive, to meet the C2Rust project’s needs.

I must STUDY this article and its knowledge more.