|
You are here |
blog.asleson.org | ||
| | | | |
blog.arcjet.com
|
|
| | | | | Building and compiling a Rust FFI library so it can be executed from Go. | |
| | | | |
scorpiosoftware.net
|
|
| | | | | The Rust language ecosystem is growing each day, its popularity increasing, and with good reason. It's the only mainstream language that provides memory and concurrency safety at compile time, with a powerful and rich build system (cargo), and a growing number of packages (crates). My daily driver is still C++, as most of my work... | |
| | | | |
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? | |
| | | | |
limpet.net
|
|
| | | [AI summary] This article explains Rust's memory safety guarantees by reframing the compiler's borrowing and lifetime checks as a system of unique versus shared access to data. | ||