2 ms·
This is a fair question really. Calling it a static analyser is misleading and seems to be editorialised. It's not like static analysers in C++. It's actually
by IshKebab 4y ago
This is a fair question really. Calling it a static analyser is misleading and seems to be editorialised. It's not like static analysers in C++.
It's actually a formal verification tool. They call it a "static verifier" not a "static analyser".
Most static analysis tools seek to find potential problems in your code - generally common mistakes - but they aren't proving anything usually. They have false positives and negatives. Formal verification requires you to write properties about your code and then it proves it.
- burjui 4y ago- I am pretty sure that static verifiers are a subclass of static analysers. - Prusti does not require you to write any "properties". I just ran it on a piece of code, which has no annotations for Prusti, and it still found a potential integer overflow. Maybe it has some internal annotations for std, but none for my code.