Document Open Access Logo

Contract Systems Need Domain-Specific Notations (Artifact)

Authors Cameron Moy , Ryan Jung , Matthias Felleisen

PDF

Artifact Description

Thumbnail PDF
PDF
DARTS.11.2.4.pdf
  • Filesize: 494 kB
  • 2 pages

Document Identifiers

Subject Classification

ACM Subject Classification
  • Software and its engineering → Domain specific languages
Keywords
  • software contracts
  • domain-specific languages

Metrics

  • Access Statistics
  • Total Accesses (updated on a weekly basis)
    0
    PDF Downloads
    0
    Metadata Views

Abstract

Contract systems enable programmers to state specifications and have them enforced at run time. First-order contracts are expressed using ordinary code, while higher-order contracts are expressed using the notation familiar from type systems. Most interface descriptions, though, come with properties that involve not just assertions about single method calls, but entire call chains. Typical contract systems cannot express these specifications concisely. Such specifications demand domain-specific notations. In response, the related article proposes that contract systems abstract over the notation used for stating specifications. It presents an architecture for such a system, some illustrative examples, and an evaluation in terms of common notations from the literature.

Cite As Get BibTex

Cameron Moy, Ryan Jung, and Matthias Felleisen. Contract Systems Need Domain-Specific Notations (Artifact). In Special Issue of the 39th European Conference on Object-Oriented Programming (ECOOP 2025). Dagstuhl Artifacts Series (DARTS), Volume 11, Issue 2, pp. 4:1-4:2, Schloss Dagstuhl – Leibniz-Zentrum für Informatik (2025) https://doi.org/10.4230/DARTS.11.2.4

Author Details

Cameron Moy
  • PLT @ Northeastern University, Boston, MA, USA
Ryan Jung
  • Northeastern University, Boston, MA, USA
Matthias Felleisen
  • PLT @ Northeastern University, Boston, MA, USA

Funding

This work was supported by NSF grant SHF 2116372.

Artifact

  MD5 Sum: 2544798173d4e73a99d1891d7b1e34b7 (Get MD5 Sum)

Artifact Evaluation Policy

The artifact has been evaluated as described in the ECOOP 2025 Call for Artifacts and the ACM Artifact Review and Badging Policy.

Related Article

Questions / Remarks / Feedback
X

Feedback for Dagstuhl Publishing


Thanks for your feedback!

Feedback submitted

Could not send message

Please try again later or send an E-mail
© 2023-2025 Schloss Dagstuhl – LZI GmbH About DROPS Imprint Privacy Contact