miniblog.

Rust has an elegant solution to testing private functions: you put the test in the file that defines the function. It generally works well. I've even seen people argue that it makes mocking much less necessary! I've not felt the need to mock in Rust so far.

Fascinating deep dive on Twitch deliberately constructing a 10GiB array to reduce the number of GC cycles in Go: https://blog.twitch.tv/en/2019/04/10/go-memory-ballast-how-i-learnt-to-stop-worrying-and-love-the-heap/ (This trick is no longer necessary in the new Go 1.19 apparently, as it's added a GOMEMLIMIT environment variable.)

Adding LLVM control flow integrity to make exploits harder is coming to Rust: https://rcvalle.com/docs/rust-cfi-design-doc.pdf The primary use case is mixing C/C++ with Rust: you have weaker memory safety guarantees and hardening is still necessary. You don't want a partial Rust port to reduce security!