package ppx_windtrap

  1. Overview
  2. Docs
PPX and instrumentation backend for windtrap

Install

dune-project
 Dependency

Authors

Maintainers

Sources

windtrap-0.2.0.tbz
sha256=2e61a86f8c97502c1f8a593c28e255d591a44b1533c6eed8cd0c847afa3d772a
sha512=060d0a47d926d420e0f96f4912c2690d148d6196bcbb701b2463a4fb9ffade5c4ff4d98d703f4b80b2b8ad1bed848c68f1d613e3ba745f9cd5e7d313e049bdc3

doc/windtrap_coverage_ppx/Windtrap_coverage_ppx/index.html

Module Windtrap_coverage_ppxSource

The registration of the coverage rewriter with the ppxlib driver.

The module exports no value, and linking it into a driver is its whole interface. When the module is initialized it registers Instrument.transform_impl_file with the ppxlib driver, under the name windtrap_coverage, as a whole-file instrumentation of implementation files.

The instrumentation is positioned after every rewriter that is not itself an instrumentation, so the function receives the expanded file and its points describe the code that runs. The one runtime dependency of the library is windtrap.runtime.

A driver may link this library and ppx_windtrap.mutate together. Of two such instrumentations ppxlib applies first the one that registered last. The driver that dune builds for a stanza naming both backends registers this library first, so the mutation rewriter runs first and this one receives its guards. Neither population is then the one that a single backend gives, and Instrument states what changes.