Abstractions can come at a COST, and while Rust is quite good at giving us zero-cost abstractions, UNDERSTANDING this can be important.
The The Cost of Indirection by Josh Mcguigan INFORMS us of this matter.
It has some example BENCHMARKS of common cases of indirection in Rust and their performance IMPACTS.
This is a matter that I think I should STUDY more.
A new release of Rust is something that I get very EXCITED about!
So I am EXCITED to read in Announcing Rust 1.41.1 that Rust 1.41.1 has been released!
GOOD WORK, Rust team!
Learning more about rustc, the Rust programming language compiler, is something I think would IMPROVE my understanding of Rust.
Understanding the performance characteristics of the rustc compiler is just ONE such way to better know it inside and out.
The Intro to rustc's self profiler article will help me LEARN about such matters, I think!
I must STUDY this more.
I knew nothing of Rust FFI unwinding but thanks to the Announcing the first FFI-unwind project design meeting announcement I now know that it is a subject that can be very COMPLEX!
I desire to LEARN more about FFI unwinding.
I KNOW of Test-Driven Development and I have heard of Domain-Driven Development, Behavior-Driven Development, Acceptance Test-Driven Development, Continuous Test-Driven Development, and Process Driven Development.
But now I have learned of ANOTHER type of driven development, and it is called Type-Driven Development!
The Introduction to Type-Driven Development with Rust gives an EXAMPLE about how to do Type-Driven Development using the Rust programming language.
I would like to see a more COMPLEX example of Type-Driven Development in action!