|
You are here |
tiemoko.com | ||
| | | | |
www.vegardno.net
|
|
| | | | | Much has been written about fuzzing compilers already, but there is not a lot that I could find about fuzzing compilers using more modern ... | |
| | | | |
borretti.me
|
|
| | | | | A survey of type systems for memory safety. | |
| | | | |
adventures.michaelfbryan.com
|
|
| | | | | Once you get past the growing pains of the Borrow Checker and realise Rust gives you the power to do things which would be unheard of (or just plain dangerous) in other languages, the temptation to Rewrite it in Rust can be quite strong. However at best, the temptation to RiiR is unproductive (unnecessary duplication of effort), and at worst it can promote the creation of buggy software (why would you be better equipped to write a library for some domain-specific purpose than the original author? | |
| | | | |
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. | ||