Surveying the Rust Verification Landscape
<|reference_start|>Surveying the Rust Verification Landscape: Rust aims to be a safe programming language applicable to systems programming applications. In particular, its type system has strong guardrails to prevent a variety of issues, such as memory safety bugs and data races. However, these guardrails can be sidestepped via the unsafe keyword. unsafe allows certain otherwise-prohibited operations, but shifts the onus of preventing undefined behaviour from the Rust language's compile-time checks to the developer. We believe that tools have a role to play in ensuring the absence of undefined behaviour in the presence of unsafe code. Moreover, safety aside, programs would also benefit from being verified for functional correctness, ensuring that they meet their specifications.   In this research proposal, we explore what it means to do Rust verification. Specifically, we explore which properties are worth verifying for Rust; what techniques exist to verify them; and which code is worth verifying. In doing so, we motivate an effort to verify safety properties of the Rust standard library, presenting the relevant challenges along with ideas to address them.<|reference_end|>
@article{blanc2024surveying,
    title={Surveying the Rust Verification Landscape},
    author={Alex Le Blanc, Patrick Lam},
    journal={arXiv preprint arXiv:2410.01981},
    year={2024},
    archivePrefix={arXiv},
    eprint={2410.01981},
    primaryClass={cs.PL}
}