Learning from the GREATEST minds is something I strive to do.
When an expert explains how to think about doing something, it can be the path to true UNDERSTANDING.
Nicholas Nethercote EXPLAINS an approach to optimizing some LEB128 handling code written in Rust.
I must STUDY this wisdom more.
Scholarly academic writings can be very DIFFERENT from the many blog articles that are written about the Rust programming language.
I find that scholarly academic papers about Rust can be harder to read and understand but I think that is because the knowledge is so much DEEPER and DENSE in scholarly academic papers.
When I do understand them I think that scholarly academic papers give me a stronger COMPREHENSION of the concepts.
Here are some scholarly academic papers about Rust that I have learned of recently but have NOT YET fully read or understood.
One is Safe Systems Programming in Rust: The Promise and the Challenge.
It has some comparisons of Rust and C++, and covers IMPORTANT topics like pointer invalidation, ownership, borrowing, references, thread safety, unsafe code, RustBelt, and more.
ANOTHER is Stacked Borrows: An Aliasing Model for Rust, and it is about things like stacked borrows and interior mutability.
I must STUDY these papers more because I think that they will make my understanding of Rust BETTER!
I am saddened to learn that Alex Crichton, one of the most PROLIFIC Rust contributors, posted this Scaling back my involvement in Rust post.
But at least Alex doesn't plan to stop ALL involvement with the Rust community: "I'll still be around in the Rust community, I'm not leaving by any measure. I mostly just plan on having my name pop up in fewer places than it currently does."
Of course I wish alexcrichton all the BEST in his future works!
The contributions Alex has made to Rust have been so IMPORTANT and I really really hope that he will continue to be a GUIDING LIGHT to show Rust the way forward!
THANK YOU, Alex!
THANK YOU!
During my recent studies of Rust I have encountered some articles about the concept of ZERO-COST ABSTRACTIONS.
One is Zero-cost abstractions in Rust by Antonin Carette, another is Rust zero cost abstractions in action by Ibrahim Dursun and discussion about it, another is Zero Cost Abstractions, and YET ANOTHER is Zero-cost futures in Rust by Aaron Turon.
Zero-cost abstractions is one of those ideas with HIDDEN complexities.
It is like an onion where peeling back one layer reveals yet more layers of STUDY that are required!
There are so many things that I have to learn about ZERO-COST ABSTRACTIONS.
I must STUDY this more!
Examining the assembly code that Rust compiler generates can be a lesson that brings WISDOM!
Amit looks at generated assembly code in the Rust memory optimization article.
It compares the assembly generated for some C++ code and some Rust code, and some KNOWLEDGE is obtained.
There can be DIFFERENCES in the number of memory accesses!
So much UNDERSTANDING can be obtained by examining the assembly code that the Rust compiler makes.