moonpool-assertions 0.8.0

Portable assertion accounting (Antithesis-style) for the moonpool framework
Documentation
  • Coverage
  • 100%
    79 out of 79 items documented0 out of 26 items with examples
  • Size
  • Source code size: 49.98 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 884.35 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 2s Average build duration of successful builds.
  • all releases: 2s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • PierreZ/moonpool
    47 3 2
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • PierreZ

Portable assertion accounting for the moonpool framework.

This is the Antithesis-style assertion suite — boolean (always / sometimes / reachable / unreachable), numeric guidance with watermarks, compound sometimes-all with frontier tracking, and per-value sometimes_each buckets — factored out of moonpool-explorer so it has zero dependencies and compiles on wasm32-unknown-unknown, macOS, and Linux.

How it relates to exploration

The counts live in a region of memory. By default [init] allocates that region on the heap (single process — wasm, macOS, plain native test runs). moonpool-explorer instead allocates a MAP_SHARED region and hands it to [install_region], so the same accounting is visible across forked children, and installs a [DiscoveryHooks] that turns "a new assertion state was reached" into coverage marking and fork dispatch. With no hooks installed the accounting is pure: assertions still record pass/fail/watermark/frontier, which is all the UntilCoverageStable stop condition and contract validation need.

See [hooks] for the coupling surface and [region] for the storage model.