I thought about that --- particularly for Firecracker, which has so much test code --- and no, it's in the actual code too.

I think Rust does more than any other mainstream language to mitigate this problem. I'm just saying, it still exists in Rust; it's just called a panic on unwrap/expect, instead of "null pointer exception".