arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2410.01981cs.PL
收藏

Rust 验证领域综述

Surveying the Rust Verification Landscape

Alex Le Blanc, Patrick Lam

AI总结:

本文综述了 Rust 验证领域,探讨了值得验证的性质、现有验证技术及值得验证的代码,并推动对 Rust 标准库安全性质的验证工作,提出相关挑战与解决思路。

摘要:

Rust 旨在成为一种适用于系统编程应用的安全编程语言。特别是,其类型系统具有强大的防护机制,以防止各种问题,例如内存安全缺陷和数据竞争。然而,这些防护机制可以通过 unsafe 关键字被绕过。unsafe 允许某些原本被禁止的操作,但将防止未定义行为的责任从 Rust 语言的编译期检查转移到了开发者身上。我们认为,在存在 unsafe 代码的情况下,工具可以在确保不存在未定义行为方面发挥作用。此外,除了安全性之外,程序还可以从功能正确性验证中受益,以确保它们满足其规范。在本研究提案中,我们探讨了进行 Rust 验证意味着什么。具体而言,我们探讨了哪些性质值得为 Rust 进行验证;存在哪些技术来验证这些性质;以及哪些代码值得验证。在此过程中,我们推动了一项验证 Rust 标准库安全性质的工作,并提出了相关挑战以及解决这些挑战的思路。

英文摘要:

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.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑