It may not be what you want but it will be “correct”.
If it compiles, you can be fairly sure it won’t exhibit unexpected behaviour. Rust requires very little runtime debugging compared to other languages. Having to perform less runtime state validation leads to cleaner, more efficient, more focused, and higher quality code. Carefully aligning application logic with Rust’s strong type rules makes APIs difficult to use incorrectly and results in simpler code that’s free from runtime checking of constraints and invariants the compiler can guarantee there are no invalid runtime code paths that will lead your program astray before it executes. The strong type system enforces these rules at compile-time. Rust offers a form of “program correctness” and many guarantees against undefined behaviour at runtime. There is a significant performance benefit to the lack of a traditional runtime we don’t have to worry about the overhead of a garbage collector, for instance. Beyond memory safety, though, there’s so much more we love about the Rust ecosystem.
One of the main things that drew us to Rust initially was the memory safety it definitely excites us knowing that Rust helps us maximize our confidence in the safety of our customers’ secrets.
