Explore >> Select a destination
|
You are here 
|
tiemoko.com | ||
| | | | |
guidovranken.com
|
|
| | | | | Cryptofuzz Cryptofuzz is a project that fuzzes cryptographic libraries and compares their output in order to find implementation discrepancies. It's quite effective and has already found a lot of bugs. Bugs in cryptographic libraries found with Cryptofuzz It's been running continually on Google's OSS-Fuzz for a while and most of the recent bugs were found... | |
| | | | |
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? | |
| | | | |
donsbot.com
|
|
| | | A common misconception from non-Haskellers is that Haskell, when compiled, pays an ongoing penalty for supporting laziness by default. The idea is that in a lazy language, every expression would suspend to a heap-allocated, garbage collected, thunk. Even if you were to use the variable immediately. That sounds scarily expensive. In the real world however,... | ||
