Explore >> Select a destination
|
You are here 
|
tiemoko.com | ||
| | | | |
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? | |
| | | | |
corrode.dev
|
|
| | | | | When people say Rust is a "safe language", they often mean memory safety. And while memory safety is a great start, it's far from all it takes to build robust applications. Memory safety is important but not sufficient for overall r... | |
| | | | |
borretti.me
|
|
| | | | | A survey of type systems for memory safety. | |
| | | | |
ochagavia.nl
|
|
| | | It's time to present the solution to the JIT calculator challenge! If you missed it, here's the original post in which I introduced it. It was a nice excuse to finally learn more about JIT compilation! I wasn't alone in this, many people were nerd-sniped into implementing their own solutions and sent me their submissions. Thanks for participating! I'll discuss them in a third blog post, to keep this one from becoming too long. | ||
