Need card #34 · Relevance High · Status New

Rust Formal Verification Tool Requirements and Pain Points

Updated 9/21/2026, 13:19:56

Problem

Developers want provable correctness in Rust, but existing tools like Verus require extra annotations and lack direct support for other languages such as .NET/C#; they are concerned about annotation overhead and toolchain integration, and aim to leverage LLMs to boost verification efficiency.

Pain points

Questions to verify

Evidence

quote · @匿名
Verus seems to be exactly what I have been looking for!
quote · @匿名
So Verus can be compiled and integrated with Rust, whereas TLA+ is used more for blueprint development that then guides the implementation in the mind of the implementer.
quote · @匿名
I have long been critical of verification tools requiring annotations. Humans cannot write correct code, so asking them to write correct proof annotations seems futile.
quote · @匿名
Does anyone now if something like this exist and is used (and actively maintained) for .NET/C#, not like Dafny where I write in another language (unlikely my company would allow that).
quote · @匿名
Ive been using Rust with LLMs for the past 2 years already... But, I will take a look at this seriously.

Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.