lawspec 0.13.0 → 0.13.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  # Native domain bindings: 0.10 acceptance scope
2
2
 
3
- Status: implementation and local acceptance complete; remote CI remains pending. The payment example now executes with
3
+ Status: implementation and acceptance complete. The payment example now executes with
4
4
  compiler-generated Rust bridges and application-library linkage. Rust supports
5
5
  generic products/sums, regular recursive mappings, nested built-in containers,
6
6
  and native Proptest factories that compose child strategies and retain shrinking.
@@ -17,7 +17,7 @@ emission requests fail explicitly.
17
17
  ## Audit of 0.9
18
18
 
19
19
  The checked-in compiler, generated API, and WASM fingerprints agree
20
- (`node tools/build-integrity.mjs`). The audit inspected the following boundaries:
20
+ (`stack run lawspec-dev -- integrity`). The audit inspected the following boundaries:
21
21
 
22
22
  | Boundary | Existing machinery | Missing for 0.10 |
23
23
  | --- | --- | --- |
@@ -955,7 +955,7 @@ CLI acceptance path: pack and install, export the payment project, prepare nativ
955
955
  dependencies, check and generate, run the normal native build tool, reject an
956
956
  incorrect fee implementation, restore application source, re-export, and check
957
957
  regeneration. Logs for every command are retained under
958
- `.artifacts/native-example-integration/`. CI runs this for every target with the
958
+ `.artifacts/native-example-integration/`. `lawspec-dev ci` runs this for every target with the
959
959
  default profile and with `LAWSPEC_MACHINE_BITS=32 LAWSPEC_MINIFY=1`.
960
960
  `LAWSPEC_PYTHON` selects the Python version for uv; an existing interpreter can be
961
961
  selected with `LAWSPEC_PYTHON_EXECUTABLE`. `LAWSPEC_NODE_MODULES` and
@@ -964,7 +964,7 @@ selected with `LAWSPEC_PYTHON_EXECUTABLE`. `LAWSPEC_NODE_MODULES` and
964
964
  Go proxy access; Stack still requires its normal configured dependency cache.
965
965
  `STACK_ROOT` and `GRADLE_USER_HOME` can select writable copies of existing caches.
966
966
 
967
- The installed CLI/native-tool path has passed for all eight targets in both CI
967
+ The installed CLI/native-tool path has passed for all eight targets in both
968
968
  configurations: 64-bit readable output and 32-bit compact output. TypeScript
969
969
  uses the exact declared dependencies recovered from the existing npm cache;
970
970
  Haskell uses a writable copy of the existing Stack cache. Kotlin's Gradle 9.3.0
@@ -991,16 +991,16 @@ The release audit maps the six shared requirements to these executable checks:
991
991
  | Resolve bindings once | `NativeBindingSpec` checks identities, complete mappings, ordering, arities, reference validation and unchanged defaults. `NativeRequestSpec` checks the public request boundary. `stack test` passes 509 examples. |
992
992
  | Checked native bridges | The target-specific native-payment, native-codec and native-shapes runners compile application models and reject incorrect conversions, precision loss, altered variants and collapsed absence. They compare native/WASM plans across machine profiles, layouts and formatting. |
993
993
  | Native generation and shrinking | The native-generator runtime checks and payment/codec runners verify framework factories, shrinking, invalid samples/shrinks, contracts and exhaustion. The shared empty-domain runners cover ignored and demanded empty parameters on all eight targets. |
994
- | Core semantics and source independence | `tools/check-boundaries.mjs` checks all eight emitter dependency boundaries. The codec/source runners build generated source without test-framework dependencies; native representations are checked against the shared schema. |
994
+ | Core semantics and source independence | `lawspec-dev boundaries` checks all eight emitter dependency boundaries. The codec/source runners build generated source without test-framework dependencies; native representations are checked against the shared schema. |
995
995
  | Application ownership | `npm/test/native-ownership.test.mjs` checks all-target migration, edited files, custom layouts, profile/format changes and adapter updates. `npm/test/native-bindings.test.mjs` covers optional generator scaffolds and signature changes. |
996
- | Coherent public interface | Schema negotiation and declarations are covered by compiler/npm tests; `tools/build-integrity.mjs` checks compiler/WASM/API fingerprints. Bundled projects are exercised by the installed-package runners. The migration guide and release notes document the interface. |
996
+ | Coherent public interface | Schema negotiation and declarations are covered by compiler/npm tests; `lawspec-dev integrity` checks compiler/WASM/API fingerprints. Bundled projects are exercised by the installed-package runners. The migration guide and release notes document the interface. |
997
997
 
998
998
  The full npm regression suite passes 77 tests, and the package smoke test passes
999
999
  installed API generation on all eight targets plus executable Rust scaffold,
1000
1000
  doctor, adapter and regeneration checks. The package contains the binding guide,
1001
1001
  migration notes, release notes and all eight application example configurations.
1002
- The remote CI gate for these checks was reviewed during the 0.11 release, which
1003
- re-ran every target job, including both installed native-binding profiles.
1002
+ These checks, including both installed native-binding profiles, are part of
1003
+ `lawspec-dev ci`, the repository's local check.
1004
1004
 
1005
1005
  The empty-parameter audit must distinguish an empty type from an inhabited type
1006
1006
  that mentions it. A native factory for `Phantom Empty` may ignore its child
package/PRIMITIVES.md CHANGED
@@ -1,4 +1,4 @@
1
- # LawSpec scalar reference (0.13.0)
1
+ # LawSpec scalar reference (0.13.2)
2
2
 
3
3
  A scalar has a declared domain, checked literals, equality, property inputs, and
4
4
  boundary fixtures. General collections, objects, pointers, and type-only constructs
@@ -142,8 +142,8 @@ portable across architectures.
142
142
  The bundled `scalars.lawspec`, `scalar_catalog.lawspec`, and
143
143
  `scalar_adapters.lawspec` contain explicit fixtures for every scalar family.
144
144
  `tools/scalar-reference.py` produces independent Fraction-based conformance
145
- vectors; `tools/scalar-integration.mjs` executes them across the eight targets.
146
- Set `LAWSPEC_MUTANTS=1` to also verify that incorrect adapters are detected.
145
+ vectors; `lawspec-acceptance scalar` executes them across the eight targets and
146
+ verifies that incorrect adapters are detected.
147
147
 
148
148
 
149
149
  Refinements, parameterized domains, abstract native integer results, and executable
package/README.md CHANGED
@@ -91,7 +91,7 @@ support to use it; GitHub currently uses the Haskell fallback.
91
91
  Install [LawSpec from npm](https://www.npmjs.com/package/lawspec):
92
92
 
93
93
  ```sh
94
- npm install --save-dev lawspec@0.13.0
94
+ npm install --save-dev lawspec@0.13.2
95
95
  npx lawspec --version
96
96
  ```
97
97
 
@@ -105,8 +105,8 @@ local dependencies so LawSpec can create its `package.json` and test script:
105
105
  ```sh
106
106
  mkdir lawspec-example
107
107
  cd lawspec-example
108
- npm exec --package=lawspec@0.13.0 -- lawspec init --target javascript
109
- npm install --save-dev lawspec@0.13.0
108
+ npm exec --package=lawspec@0.13.2 -- lawspec init --target javascript
109
+ npm install --save-dev lawspec@0.13.2
110
110
  npx lawspec check
111
111
  npx lawspec explain 'example.atoi_codec::itoa and then atoi yields a'
112
112
  npx lawspec doctor
@@ -316,7 +316,7 @@ reusable laws accept these curried functions, their partial applications, and
316
316
  scalar parameters. Quantified test inputs remain scalar.
317
317
 
318
318
  The prelude defines the following laws. Every row has an executable example in
319
- [algebra.lawspec](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/algebra.lawspec), including both sides of every
319
+ [algebra.lawspec](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/algebra.lawspec), including both sides of every
320
320
  combined law. `f` and `g` are binary operations, `inverse` is unary, and `e` and
321
321
  `zero` are scalar parameters. All these laws require equality of the element type.
322
322
 
@@ -384,7 +384,7 @@ their entire consequence. Every conjunct is type-checked and emitted. As with
384
384
  existing assertions, the first failure stops that individual test. `and` is now
385
385
  a reserved word.
386
386
 
387
- [Currying examples](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/currying.lawspec) demonstrate a four-argument
387
+ [Currying examples](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/currying.lawspec) demonstrate a four-argument
388
388
  function partially applied twice, a formatter with four heterogeneous arguments,
389
389
  and composition after partial application. Each example states its exact outputs.
390
390
  Run `node npm/bin/lawspec.mjs examples` after rebuilding to inspect all nine units
@@ -436,7 +436,7 @@ law `valid ports round trip` is
436
436
  end
437
437
  ```
438
438
 
439
- The [complete port example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/parse_port.lawspec)
439
+ The [complete port example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/parse_port.lawspec)
440
440
  defines valid ports as 1–65535, and covers both endpoints, ordinary ports, zero,
441
441
  negative values, and 65536. All explicit `expect` assertions run regardless of
442
442
  the law's condition. A false condition skips only the consequence: invalid ports
@@ -454,7 +454,7 @@ The prelude includes `satisfies predicate` (the predicate holds for every input)
454
454
  and `left inverse when predicate parse render` (the guarded round trip above).
455
455
  These reusable laws preserve the condition and its lexical bindings when expanded.
456
456
  `equivalent` can also compare two predicates, since `Bool` supports equality.
457
- The [Boolean flags example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/boolean_flags.lawspec)
457
+ The [Boolean flags example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/boolean_flags.lawspec)
458
458
  checks that flipping twice restores both `false` and `true`; all targets generate
459
459
  Boolean property inputs and explicit tests for both Boolean boundary values. Java caps Boolean-only JetCheck runs at the number of
460
460
  possible input combinations (up to 100), avoiding generator exhaustion.
@@ -533,7 +533,7 @@ This expands to `for all (x :: Int32) . render (x) = referenceRender (x)`.
533
533
  The example inherits the input name `x` from the prelude. Both functions are
534
534
  user-owned adapter functions; either may delegate to your existing code.
535
535
 
536
- [The complete example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/equivalent.lawspec) compares decimal
536
+ [The complete example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/equivalent.lawspec) compares decimal
537
537
  renderers and two implementations that clamp negative integers to zero. For
538
538
  JavaScript, their adapters can be:
539
539
 
@@ -570,7 +570,7 @@ law `normalizers agree` is
570
570
  end
571
571
  ```
572
572
 
573
- The [slug example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/slug.lawspec)
573
+ The [slug example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/slug.lawspec)
574
574
  compares two implementations of ASCII-space replacement. It includes empty,
575
575
  Unicode and escaped text. Each target uses its native string generator:
576
576
  JetCheck `Generator.stringsOf(Generator.asciiPrintableChars())`, Hypothesis `st.text()`, fast-check `fc.string()`,
@@ -597,7 +597,7 @@ law `canonicalization reaches a fixed point` is
597
597
  end
598
598
  ```
599
599
 
600
- The [canonical URL example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/canonical_url.lawspec)
600
+ The [canonical URL example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/canonical_url.lawspec)
601
601
  uses removal of **all trailing slashes** as a small fixed-point demonstration,
602
602
  not a complete URL canonicalization algorithm. For JavaScript:
603
603
 
@@ -606,7 +606,7 @@ export const canonicalize = value => value.replace(/\/+$/, "");
606
606
  ```
607
607
 
608
608
  Removing just one trailing slash fails the supplied repeated-slash example.
609
- The [mixed-input example](https://github.com/brain-fuel/lawspec/blob/v0.13.0/examples/specs/mixed_inputs.lawspec)
609
+ The [mixed-input example](https://github.com/brain-fuel/lawspec/blob/v0.13.2/examples/specs/mixed_inputs.lawspec)
610
610
  shows `Text` and `Int32` in the same quantified property and executable example.
611
611
  The JavaScript API represents example bindings as typed records whose values use
612
612
  `DataValue`: lossless tagged scalar payloads or structural constructors. Expected results are
@@ -689,7 +689,7 @@ by the JS shim.
689
689
  ## Build and verify
690
690
 
691
691
  For contributors working from a repository checkout, build a local archive with
692
- `npm pack ./npm` and install it with `npm install --save-dev ./lawspec-0.13.0.tgz`.
692
+ `npm pack ./npm` and install it with `npm install --save-dev ./lawspec-0.13.2.tgz`.
693
693
  The package payload lives in `npm/`.
694
694
 
695
695
  ```sh
@@ -698,7 +698,7 @@ stack test
698
698
  tools/wasm.sh
699
699
  node --test npm/test/*.test.mjs
700
700
  node tools/parity.mjs
701
- node tools/build-integrity.mjs
701
+ stack run lawspec-dev -- integrity
702
702
  node tools/package-smoke.mjs
703
703
  ```
704
704
 
@@ -709,24 +709,48 @@ are frozen in `wasm/cabal.project.freeze`. Install the cross compiler through
709
709
  [ghc-wasm-meta](https://gitlab.haskell.org/haskell-wasm/ghc-wasm-meta).
710
710
 
711
711
  Haskell's export table generates the JS API and `.d.ts` files. The build records
712
- compiler-source and artifact hashes in `npm/build.json`; CI rejects stale WASM
713
- or hand-edited generated wrappers. The npm archive is a self-contained consumer
712
+ compiler-source and artifact hashes in `npm/build.json`; `lawspec-dev integrity`
713
+ rejects stale WASM or hand-edited generated wrappers. The npm archive is a self-contained consumer
714
714
  artifact, with no install-time compilation or download hook.
715
715
 
716
- For all eight native integrations, install their build tools, then:
716
+ The complete check runs locally; there is no hosted CI. Install the eight
717
+ targets' build tools, then:
718
+
719
+ ```sh
720
+ stack run lawspec-dev -- ci # everything
721
+ stack run lawspec-dev -- ci --target rust --target go
722
+ stack run lawspec-dev -- ci --core # compiler, npm and editor only
723
+ ```
724
+
725
+ It runs the compiler, npm, parity, package and editor checks, then for each
726
+ target bootstraps its dependencies, runs every acceptance suite in both machine
727
+ profiles, and runs the installed native-binding example. Each step logs to
728
+ `.artifacts/ci/`, and the command exits non-zero if any step failed.
729
+ `--rust-toolchains 1.85.0,stable` and `--rust-targets i686-unknown-linux-gnu`
730
+ add Rust toolchains and architectures. The steps can also be run on their own:
717
731
 
718
732
  ```sh
719
- # Set LAWSPEC_GRADLE to a Gradle 9.3.0 executable if it is not on PATH.
720
733
  node tools/bootstrap-integration.mjs
721
- node tools/integration.mjs
734
+ stack run lawspec-acceptance -- integration # all eight targets
735
+ stack run lawspec-acceptance -- scalar rust # one suite, one target
736
+ LAWSPEC_MACHINE_BITS=32 LAWSPEC_MINIFY=1 stack run lawspec-acceptance -- indexed go
737
+ stack run lawspec-acceptance -- domain --check # regenerate and compare only
722
738
  ```
723
739
 
724
- These scripts use isolated `.integration/` projects. Bootstrap installs the pinned
725
- test dependencies; integration verifies that correct adapters pass, broken adapters
726
- fail, regeneration preserves implementations, and generation leaves build files
727
- unchanged. Arguments select individual targets. `LAWSPEC_PYTHON=3.14` selects the
728
- additional Python reference environment. CI also exercises Node 22/24/26 and packs
729
- and installs the npm archive. Registry publication is a separate release action.
740
+ Bootstrap installs the pinned test dependencies into isolated `.integration/`
741
+ projects. `lawspec-acceptance` generates each suite's bundled examples in process,
742
+ installs the suite's adapters, runs the target's own test command, and requires
743
+ every mutant to fail its laws at test time; a mutant that only breaks the build
744
+ fails the suite. Suites live in `acceptance/<suite>/`: `suite.json` names the
745
+ specifications, `<target>/files/` holds real adapter sources, `<target>/stubs/`
746
+ records the stub an adapter was written against, and `<target>/mutants/*.mutant`
747
+ holds one search/replace edit per mutant. Suites are `integration`, `algebra`,
748
+ `scalar`, `refinement`, `indexed` and `domain`. Gradle 9.3.0 is used from
749
+ `.tools/gradle-9.3.0` when present, otherwise from `PATH`; `LAWSPEC_OFFLINE=1`
750
+ uses existing dependency caches. `npm/test/build-files.test.mjs` checks that
751
+ generation leaves build files unchanged. `LAWSPEC_PYTHON=3.14` selects the
752
+ additional Python reference environment. Registry publication is a separate
753
+ release action.
730
754
 
731
755
  The native-binding acceptance command uses the installed npm archive, public CLI,
732
756
  and the selected target's normal test command:
package/REFINEMENTS.md CHANGED
@@ -1,4 +1,4 @@
1
- # Refinements and abstract integers (0.13.0)
1
+ # Refinements and abstract integers (0.13.2)
2
2
 
3
3
  A refinement restricts a scalar domain with a pure Boolean expression. LawSpec
4
4
  checks concrete examples, generates satisfying input tuples, and checks adapter
package/RELEASE-0.13.md CHANGED
@@ -1,6 +1,48 @@
1
- # LawSpec 0.13.0
1
+ # LawSpec 0.13
2
2
 
3
- ## Wrappers and constrained primitives
3
+ ## 0.13.2
4
+
5
+ A maintenance release. The language, generated code and API are unchanged.
6
+
7
+ - The repository has no hosted CI. `stack run lawspec-dev -- ci` runs the
8
+ complete check locally: compiler, npm, parity, package and editor checks, then
9
+ for each target the dependency bootstrap, every acceptance suite in both
10
+ machine profiles, and the installed native-binding example. It logs each step to
11
+ `.artifacts/ci/` and exits non-zero on any failure. `--target`, `--core`,
12
+ `--fail-fast`, `--rust-toolchains` and `--rust-targets` select what to run.
13
+ `make ci` is equivalent.
14
+ - The JavaScript acceptance runners and fixture modules replaced by
15
+ `lawspec-acceptance` are removed.
16
+ - The package smoke test's per-command timeout is ten minutes: exporting every
17
+ bundled example had exceeded the former two-minute limit on slower machines.
18
+ - The integration bootstrap restores missing scaffold files in existing projects.
19
+
20
+ ## 0.13.1
21
+
22
+ A maintenance release. The language, generated code and API are unchanged from
23
+ 0.13.0.
24
+
25
+ - Repository checks move from JavaScript to Haskell. `lawspec-dev boundaries` and
26
+ `lawspec-dev integrity` replace `tools/check-boundaries.mjs` and
27
+ `tools/build-integrity.mjs`. The integrity check now also rejects staged npm
28
+ copies of documentation and examples that differ from their sources.
29
+ - `lawspec-acceptance` runs the bundled-example acceptance suites
30
+ (`integration`, `algebra`, `scalar`, `refinement`, `indexed`, `domain`) in
31
+ process. Adapters and mutants are real files under `acceptance/`, and a
32
+ mutant that only breaks the build now fails the suite. This exposed a
33
+ TypeScript scalar mutant that previously counted as rejected because it
34
+ failed type-checking; it now exercises the laws. The JavaScript runners
35
+ continue to run alongside it in CI.
36
+ - Build-file scaffolds are defined once in Haskell (`LawSpec.Scaffold`) and
37
+ checked against the npm templates byte for byte.
38
+ - Compiler API contract tests formerly in `npm/test` run in hspec against the
39
+ same JSON boundary that `core.wasm` exports. A new npm test checks that
40
+ generation never rewrites build files and that regeneration is a no-op on
41
+ every target.
42
+
43
+ ## 0.13.0
44
+
45
+ ### Wrappers and constrained primitives
4
46
 
5
47
  ```lawspec
6
48
  wrapper UnitQuantity is Int32 where value >= 1 && value <= 1000 end
@@ -15,7 +57,7 @@ value. Wrappers may take type parameters. They elaborate to a single-constructor
15
57
  product with a refined field, so all eight targets represent them natively with
16
58
  no new runtime machinery.
17
59
 
18
- ## Workflows and state distinctions
60
+ ### Workflows and state distinctions
19
61
 
20
62
  ```lawspec
21
63
  workflow placeOrder :: UnvalidatedOrder -> Either OrderError PricedOrder is
@@ -32,14 +74,14 @@ native workflow must equal the railway composition of the native steps.
32
74
  Diagnostics name the step and the mismatched types, with the workflow's source
33
75
  location.
34
76
 
35
- ## Evidence
77
+ ### Evidence
36
78
 
37
79
  Constructor field constraints, including wrapper constraints, appear in the
38
80
  evidence as `construction` obligations with status `runtime-checked`, next to
39
81
  the contract obligations introduced in 0.12. The TypeScript API declares these
40
82
  records as `ObligationEvidence`; the 0.12 typing was not published.
41
83
 
42
- ## Examples and acceptance
84
+ ### Examples and acceptance
43
85
 
44
86
  `examples/specs/domain_modeling.lawspec` combines wrappers, a parameterized
45
87
  `NonEmptyList`, order states and the workflow. `tools/domain-integration.mjs`
@@ -48,7 +90,7 @@ mutants that break a wrapper invariant, the railway composition, or a non-empty
48
90
  list operation fail. The example runners now share
49
91
  `tools/example-acceptance.mjs`.
50
92
 
51
- ## Compatibility
93
+ ### Compatibility
52
94
 
53
95
  `wrapper` and `workflow` begin new declarations. Specifications that do not use
54
96
  them compile as in 0.12. API schemas 3 and 4 are unchanged, apart from the
package/bin/lawspec.mjs CHANGED
@@ -173,13 +173,13 @@ async function main() {
173
173
  }
174
174
  if (!verb || ["help", "--help", "-h"].includes(verb)) {
175
175
  output(
176
- "LawSpec 0.13.0\nUsage: lawspec init --target <language> [--project <directory>] [--minify]\n lawspec check | doctor | explain <unit>::<law> | generate\n lawspec examples [--example payments] [--target <language>] [--output <directory>]\nOptions: --config <path>, --target <language>, --machine-bits <32|64>, --json\nGeneration: --dry-run, --check, --minify\nTargets: " +
176
+ "LawSpec 0.13.2\nUsage: lawspec init --target <language> [--project <directory>] [--minify]\n lawspec check | doctor | explain <unit>::<law> | generate\n lawspec examples [--example payments] [--target <language>] [--output <directory>]\nOptions: --config <path>, --target <language>, --machine-bits <32|64>, --json\nGeneration: --dry-run, --check, --minify\nTargets: " +
177
177
  targets.join(", "),
178
178
  );
179
179
  return;
180
180
  }
181
181
  if (verb === "--version") {
182
- output("0.13.0");
182
+ output("0.13.2");
183
183
  return;
184
184
  }
185
185
  if (positional.length > (verb === "explain" ? 1 : 0))
package/build.json CHANGED
@@ -112,6 +112,7 @@
112
112
  "src/LawSpec/RustExpr.hs",
113
113
  "src/LawSpec/RustNativeBinding.hs",
114
114
  "src/LawSpec/RustNativeGenerators.hs",
115
+ "src/LawSpec/Scaffold.hs",
115
116
  "src/LawSpec/Scalar.hs",
116
117
  "src/LawSpec/SpecializeDefinitions.hs",
117
118
  "src/LawSpec/Testing.hs",
@@ -129,8 +130,8 @@
129
130
  "wasm/lawspec-wasm.cabal"
130
131
  ],
131
132
  "digests": {
132
- "lawspec.cabal": "2aab726a6d4e9c64e218c0563d52fab738b0753f9597683b9d650dde1baa948c",
133
- "package.yaml": "95807129285b33f8ac2bf7452aae1ee049f8f7711f0dc9f962fdf9586b58fcc8",
133
+ "lawspec.cabal": "88e838807acd277e0e8935016e1fef69a833077f4d71f124c90dc82595a38ff1",
134
+ "package.yaml": "63da3402b545fee063873916cbf7a1a21043a7c2a66424d0be715b28e4e2d590",
134
135
  "runtime/LawSpecCodecs.hs": "90cb1ed15d7ab664a17a054580c849408d77cfd2b2adcb4a3228b05132caeaca",
135
136
  "runtime/LawSpecDataStrategies.hs": "cbe9f1946228db1076c19cd3158e8798fe32766cfdbea3f66b63d22d3d217508",
136
137
  "runtime/LawSpecDataStrategies.java": "e3416efe8a0d7b1276cb4d1a8105fd01b1f5f3f02a803bf55d955d9e3ec39095",
@@ -154,8 +155,8 @@
154
155
  "runtime/lawspec_schema.mjs": "60eb4204461eaa2c207fc7c3394014e2a814e4383b7045c065b4dae7c7a202c2",
155
156
  "runtime/lawspec_schema.py": "b6967ef1a33fe6a1a180d5573ec37cd8bb2079c06e961ac2eeb05f23cffcdd07",
156
157
  "runtime/lawspec_strategies.rs": "cac9ca301d4614fff9acfe61e7cc5678fabc044edadfa89ec11599b6780dc5f3",
157
- "runtime/rust/Cargo.lock": "deb6b268124278aa237f64c8e821caf2388ccda3df92c2e814a5863331ae8c92",
158
- "runtime/rust/Cargo.toml": "ed36668f25943b9c8a3ea9eb5a805f2953540aabb763919029947d342cc23978",
158
+ "runtime/rust/Cargo.lock": "17f3a870021e47b128578e6a4e2467ac02376584b89b851daa6280fbeda23abf",
159
+ "runtime/rust/Cargo.toml": "f3737514e8a696bdfcf496c483d03aab9dda0c9fc6cf07b8a6ec300d9b0d8e15",
159
160
  "src/LawSpec/Api.hs": "392f6e8c1a9ae81a95e219ac071e5b4bea03ee330d63b829036f8f54b2eda8a7",
160
161
  "src/LawSpec/Backend.hs": "03c3b0cd62467ca677c88d29d7b12b2ab505cc0076d93d1f48fbddb0e9bcf133",
161
162
  "src/LawSpec/Capabilities.hs": "e43d4fc3a4481fbb8aa3ff1c3f41f7e7fca5db01bfe256a30162a45d75a00c1c",
@@ -240,6 +241,7 @@
240
241
  "src/LawSpec/RustExpr.hs": "04b2ef81417b811c7b98a98acdadab4e588ca8757964a63ba8dc5936c36479e6",
241
242
  "src/LawSpec/RustNativeBinding.hs": "9d08348da571ac335e335e48c1ad4a67108f7bca54119f5960480e97a6d1da84",
242
243
  "src/LawSpec/RustNativeGenerators.hs": "a3b1484d9ff0008e4f961aa81d0aa51da57ec0cd7909124e80c98d56aacc8ce9",
244
+ "src/LawSpec/Scaffold.hs": "2cdaeaa0708803e6abf3b8e9062dfc2fe31e2d3a6df3b252a17b1ad91eb5d8f2",
243
245
  "src/LawSpec/Scalar.hs": "52e61fec81a337bb5b35e9e6f501446cf0b18bffa6c6af2ddc5aeac2d6e07131",
244
246
  "src/LawSpec/SpecializeDefinitions.hs": "08f2fe674a5e00d1be396d9edab0dd2c948b7beb12fa99f2a6aba00cbdf01e33",
245
247
  "src/LawSpec/Testing.hs": "7b0a2e58bcef24365883b479b6a5af720cc2ac4c217ae23bb771c2621d82aec3",
@@ -254,8 +256,8 @@
254
256
  "wasm/app/Exports.hs": "4ecbdac8faa2449e6fc61b93c82e6278fa14374154f29b4dacf0eef433f06a47",
255
257
  "wasm/cabal.project": "021e560afdc5eb4cb7169e7119ecb8f92c9ee170245af909c94b612941bff5cc",
256
258
  "wasm/cabal.project.freeze": "733dbed3d2ecccb26e874fd58f136296dad772184deb1658c196b5d54a0814dc",
257
- "wasm/lawspec-wasm.cabal": "ee8235aa57e891fe5b1f0d798694f5db5bc6e83b4d013fd1a96e9b2d28aae613",
258
- "npm/core.wasm": "f67a99e2de93750f0d4930cc086688a74ee1d309c3818bfe3125490e01b08660",
259
+ "wasm/lawspec-wasm.cabal": "5ca5b6f2ed98be3095c0f1f2233efbe13f61f2a13dd111936c5c956df0fd1725",
260
+ "npm/core.wasm": "16f17510da392bc8fff7d4cbcb34abab2fa0e45abd4a9d4f4d62bf0ffb19cff5",
259
261
  "npm/core_jsffi.js": "88d136efe92f7cff5758c8fec8d9b6bbc9707fe37741cebeeb415fe34ce3d72b",
260
262
  "npm/api.mjs": "e93251db289ff0609abaff78ad67f0a9af82508c1141c6a999604f67c56b6e7d",
261
263
  "npm/index.d.ts": "2674f8830bd20a2b9ef7dfa99e183598125b6bcc17e8d454e8f7cca1bbd2c9fe"
package/core.wasm CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lawspec",
3
- "version": "0.13.0",
3
+ "version": "0.13.2",
4
4
  "description": "State the law once. Check it everywhere.",
5
5
  "license": "MIT",
6
6
  "type": "module",