Over the past twenty-five years, higher-order contracts have become a well-established mechanism for enforcing software specifications. Such contracts interact with higher-order values (e.g., functions and objects). While these interactions may look benign at first, they can cause all kinds of effects—nontermination, resource consumption, writing to output devices—all of which are undesirable.
In response, this paper presents lackadaisical contract checking. Concretely, interactions with higher-order values in contract code (e.g., function applications and method calls) are deferred until the program itself demands the same interaction. A model of this semantics satisfies critical metatheoretic properties: an erasure theorem, the blame soundness theorem, and the complete monitoring property. Its implementation validates that the idea can be realized within a production-grade contract system.