Combining Static and Dynamic Contract Checking for Curry — mentioned by rrobukef

Wed, 17 Apr 2019 16:12:16 GMT

Deductive verification is a large extension of designing by contract: The addition of a SMT solver to verify the contracts at compile time for instance. On the other hand libhoare only adds the contracts as a runtime addition with no mention of formally verifying these. The same with the RFC, it dismissed automatic verification: "Automated proof systems are very hard, especially when AFAIK Rust's type system doesn't even have partial formal proofs yet." This paper shows a similar approach to OP's but applied to Curry: https://arxiv.org/abs/1709.04816. It shows how no formal proofs are needed.…

Paper and discussion history. A mention is not an endorsement.

Combining Static and Dynamic Contract Checking for Curry · HackerPapers discussions

Combining Static and Dynamic Contract Checking for Curry — mentioned by rrobukef