/explore
|
You are here 
|
gavinhoward.com | ||
| | | | |
nora.codes
|
|
| | | | | [AI summary] The article explains the concept of 'unsafe' in Rust, clarifying that it allows specific low-level operations while maintaining overall memory safety through the language's type system and safe abstractions. | |
| | | | |
viralinstruction.com
|
|
| | | | | [AI summary] The author argues that Rust's borrowchecker causes serious ergonomic problems and overstates its role in memory safety, suggesting that the effort required to satisfy it often outweighs the benefits compared to garbage-collected languages. | |
| | | | |
www.thecodedmessage.com
|
|
| | | | | The NSA recently published a Cybersecurity Information Sheet about the importance of memory safety, where they recommended moving from memory-unsafe programming languages (like C and C++) to memory-safe ones (like Rust). Dr. Bjarne Stroustrup, the original creator of C++, has made some waves with his response. To be honest, I was disappointed. As a current die-hard Rustacean and former die-hard C++ programmer, I have thought (and blogged) quite a bit about the topic of Rust vs C++. | |
| | | | |
joeprevite.com
|
|
| | | My notes from Chapter 4 of the Rust Lang Book. | ||
