Cranston's Life - Rust and More Rust

The article The problem of effects in Rust got me THINKING about Rust and effects.

The article says that Rust has an "excellent system for managing effects related to mutation and memory" but also that Rust 1.0 has "no native facility for managing effects related to control flow", and this really got me THINKING.

Effects that the article lists like fallibility, multiplicity, and asynchrony are so IMPACTFUL when writing Rust code.

I must STUDY this more so that I have better knowledge about effects and Rust.

Will Crichton gracious SHARES with us some thoughts about extensible software architectures and using types instead of strings in them in the Types Over Strings: Extensible Architectures in Rust article.

Defining frameworks of other extensible architectures in a way that makes them TYPE SAFE is something that I support!

I must STUDY the thoughts of Will's article to better understand this matter because I think it is IMPORTANT!

Because of the article A Possible New Backend for Rust by Jason Williams I now know of what I think is an EXCITING development!

The article explains how Rust's compiler uses LLVM as a backend and this could be INFORMATIVE for somebody who is new to Rust.

But the SPEED of Rust compilation is an issue for many Rust programmers.

Some Rust programmers want Rust code to compile FASTER.

This article explains the efforts of using Cranelift in the Rust compiler backend for FASTER compilation!

I too have found Rust to compile too slowly sometimes and if there is something that can SPEED UP Rust compilation and REDUCE the time I wait for my Rust code to compile then I am very EXCITED to learn more about it!

Iteration is a very IMPORTANT topic.

The Fallible Iterator Adapters article by Yoshua Wuyts gives us some things about iterators to THINK about.

It gives consideration and INSIGHT about the various adaptors that std::iter::Iterator provides.

I must STUDY this more, because Rust iterators are something I should know so much more about.

In the article How often does Rust change?, Steve Klabnik SHARES with us some data collections about how often Rust changes.

This is the kind of matter that is hard to do a pure science analysis of but I think that Steve has done what can be done to get a DATA DRIVEN understanding of the situation.

Because Rust has grown and changed over MANY YEARS I think it can be so hard to see the change, but I also think that Steve has FOUND possibly a way to do it!

There are some discussions about these findings too.

Steve, I must also say that I hate how the article's date FADES away because it is so DISTRACTING and it makes it HARDER to see when the article was written!

But that aside I must STUDY Steve's findings more to understand how the Rust programming language CHANGES over time.