<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-07-23T17:33:49Z</responseDate>
  <request identifier="6102" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:6102</identifier>
        <datestamp>2024-03-06T10:37:59Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>C++ const and Immutability: An Empirical Study of Writes-Through-const</dc:title>
          <dc:creator>Eyolfson, Jon</dc:creator>
          <dc:creator>Lam, Patrick</dc:creator>
          <dc:subject>empirical study</dc:subject>
          <dc:subject>dynamic analysis</dc:subject>
          <dc:subject>immutability</dc:subject>
          <dc:description>The ability to specify immutability in a programming language is a&#13;
powerful tool for developers, enabling them to better understand and&#13;
more safely transform their code without fearing unintended changes to program state.  The C++ programming language allows developers to&#13;
specify a form of immutability using the const keyword. In this work, we characterize the meaning of the C++ const qualifier and present the ConstSanitizer tool, which dynamically verifies a stricter form of immutability than that defined in C++: it identifies const uses that are either not consistent with transitive immutability, that write to mutable fields, or that write to formerly-const objects whose const-ness has been cast away.&#13;
&#13;
We evaluate a set of 7 C++ benchmark programs to find writes-through-const, establish root causes for how they fail to respect our stricter definition of immutability, and assign attributes&#13;
to each write (namely: synchronized, not visible, buffer/cache,&#13;
delayed initialization, and incorrect). ConstSanitizer finds 17&#13;
archetypes for writes in these programs which do not respect our&#13;
version of immutability. Over half of these seem unnecessary to us.&#13;
Our classification and observations of behaviour in practice&#13;
contribute to the understanding of a widely-used C++ language feature.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Jon Eyolfson and Patrick Lam</dc:contributor>
          <dc:date>2016</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 56, 30th European Conference on Object-Oriented Programming (ECOOP 2016)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ECOOP.2016.8</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-61024</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ECOOP.2016.8</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
