Measure What You Optimize - Cliffle

Learn Rust the Dangerous Way, Part 3

Learn Rust the Dangerous Way, Part 3 2019-12-09 Refreshing your (uninitialized) memory Measuring A safe version of output_Energy What have we learned? Where next? (Series Overview) In part 2 we introduced Rust references, and this was enough to convert one of our inner functions into safe Rust. The others are still unsafe. There are several reasons for this. In this, the briefest of sections, we’ll tackle the easiest one: deliberate use of uninitialized memory. Refreshing your (uninitialized) memory At the end of part 2, our program looked like this: nbody-2.rs There are two…

saved by

• agniv sarkar

related reading

• Learn Rust the Dangerous Waycliffle.com
• Memory safety and ownership - Rust for C-Programmersrust-for-c-programmers.com
• Destroy All Values: Designing Deinitialization in Programming Languages - Faultloregankra.github.io
• Rewriting Bun in Rust | Bun Blogbun.com
• Rust Optimization.md · GitHubgist.github.com
• A half-hour to learn Rustfasterthanli.me
• What is Ownership? - The Rust Programming Languagerust-book.cs.brown.edu
• Rust Language Cheat Sheetcheats.rs
• (Re)writing an interpreter in Rust – Danny van Kootendannyvankooten.com
• abseil / Performance Hintsabseil.io
• What Every C Programmer Should Know About Undefined Behavior #2/3 - The LLVM Project Blogblog.llvm.org
• Rust for C programmers - Rust for C-Programmersrust-for-c-programmers.com