Prusti: Static Analyzer for Rust
github.com
Prusti: Static Analyzer for Rust
1–10 of 93 posts
Re: Prusti: Static Analyzer for Rust
#2Re: Prusti: Static Analyzer for Rust
#3Re: Prusti: Static Analyzer for Rust
#4What are people's experiences with static analyzers at companies? Many people I have spoken with have either never heard of them, or expressed no interest. Usually those same people use dynamic languages like Ruby or Python.
- https://fbinfer.com/ (- https://github.com/google/error-prone
- https://github.com/facebook/SPARTA
And many others
Re: Prusti: Static Analyzer for Rust
#5What are people's experiences with static analyzers at companies? Many people I have spoken with have either never heard of them, or expressed no interest. Usually those same people use dynamic languages like Ruby or Python.
Re: Prusti: Static Analyzer for Rust
#6What are people's experiences with static analyzers at companies? Many people I have spoken with have either never heard of them, or expressed no interest. Usually those same people use dynamic languages like Ruby or Python.
Re: Prusti: Static Analyzer for Rust
#7What are people's experiences with static analyzers at companies? Many people I have spoken with have either never heard of them, or expressed no interest. Usually those same people use dynamic languages like Ruby or Python.
Re: Prusti: Static Analyzer for Rust
#8Re: Prusti: Static Analyzer for Rust
#9Why would you need a static analyzer for a language that promotes itself as safe out of the box.
Re: Prusti: Static Analyzer for Rust
#10Why would you need a static analyzer for a language that promotes itself as safe out of the box.
Rust checks integer overflows at runtime (or not at all, if building for maximum speed). It is safer than not checking at all. But costs performance and can lead to (predictable) crashes.
This tool is a way to prove that overflows can not happen at compile time. Which is extremely hard in the general case.