What's your strategy for checking that your code is panic free?

This page summarizes the projects mentioned and recommended in the original post on /r/rust
Rust Verification Viper Formal Verification

WorkOS
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors

  • prusti-dev

    A static verifier for Rust, based on the Viper verification infrastructure.

    • See also https://github.com/viperproject/prusti-dev

  • rustig

    A tool to detect code paths leading to Rust's panic handler (by MichaelMauderer)

    • The approaches I've seen (Rustig, findpanics, no-panic, dont_panic) tend to be based around using whole-program analysis on the generated output binary to determine what's calling the panic machinery once the optimizers have had their way with it.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo

  • findpanics

    Find calls to panic functions in rust executables

    • The approaches I've seen (Rustig, findpanics, no-panic, dont_panic) tend to be based around using whole-program analysis on the generated output binary to determine what's calling the panic machinery once the optimizers have had their way with it.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts