A non-interactive verifier like VerCors or OpenJML, will let users spend considerable time waiting to see if everything still verifies. We build a preprocessor for such tools that slices a single file into several independently verifiable files, calls the verifier in parallel, and caches the results. We call our tool SplitVerify. SplitVerify uses dependency analysis and whitespace/comment reduction, to increase the chance that the verification of a part of the project is cached. The tool is built using Haskell, using a bidirectional semi-language-agnostic parser and generic programming to keep SplitVerify lightweight and maintainable. As of today, SplitVerify uses only 752 lines of code (counted with cloc).
Thursday 19 December 2019 15:45 - 16:30
More events
- Mon 15 Sep 2025 10:00 - 11:00Infosession parttime programme Digital Design & Architecture
- Mon 15 Sep 2025 17:30 - 20:00Pioneers in HealthCare Matchmaking event
- Tue 16 Sep 2025 19:30 - 21:00In search of a new world order
- Thu 18 Sep 2025 20:00 - 22:00Native trees first?
- Tue 23 Sep 2025 19:30 - 21:00Cooperating with the army?