Building contract support into the language makes for:
1) a consistent look and feel for the contracts
2) tool support
3) it's possible the compiler can generate better code using information gathered
from the contracts
4) easier management and enforcement of contracts
5) handling of contract inheritance
The idea of a contract is simple - it's just an expression that must evaluate to true. If it does not, the contract is broken, and by definition, the program has a bug in it. Contracts form part of the specification for a program, moving it from the documentation to the code itself. And as every programmer knows, documentation tends to be incomplete, out of date, wrong, or non-existent. Moving the contracts into the code makes them verifiable against the program.
The most basic contract is the assert. An assert inserts a checkable expression into the code, and that expression must evaluate to true:
assert(expression);C programmers will find it familiar. Unlike C, however, an
assert
in function bodies
works by throwing an AssertException
,
which can be caught and handled. Catching the contract violation is useful
when the code must deal with errant uses by other code, when it must be
failure proof, and as a useful tool for debugging.
The pre contracts specify the preconditions before a statement is executed. The most typical use of this would be in validating the parameters to a function. The post contracts validate the result of the statement. The most typical use of this would be in validating the return value of a function and of any side effects it has. The syntax is:
in { ...contract preconditions... } out (result) { ...contract postconditions... } body { ...code... }By definition, if a pre contract fails, then the body received bad parameters. An InException is thrown. If a post contract fails, then there is a bug in the body. An OutException is thrown.
Either the in
or the out
clause can be omitted.
If the out
clause is for a function
body, the variable result
is declared and assigned the return
value of the function.
For example, let's implement a square root function:
long square_root(long x) in { assert(x >= 0); } out (result) { assert((result * result) == x); } body { return math.sqrt(x); }The assert's in the in and out bodies are called contracts. Any other D statement or expression is allowed in the bodies, but it is important to out that the code has no side effects, and that the release version of the code will not depend on any effects of the code. For a release build of the code, the in and out code is not inserted.
If the function returns a void, there is no result, and so there can be no result declaration in the out clause. In that case, use:
void func() out { ...contracts... } body { ... }In an out statement, result is initialized and set to the return value of the function.
The compiler can be adjusted to verify that every in and inout parameter is referenced
in the in { }
,
and every out and inout parameter is referenced in the out { }
.
The in-out statement can also be used inside a function, for example, it can be used to check the results of a loop:
in { assert(j == 0); } out { assert(j == 10); } body { for (i = 0; i < 10; i++) j++; }This is not implemented at this time.
Conversely, all of the out contracts needs to be satisified, so overriding functions becomes a processes of tightening the out contracts.