hegeltest 0.3.0-x86_64-linux → 0.3.1-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a6d0f9ced2d7fcce11d764297e9e916389c5eb006835598e36ccadd72569c9e9
-  data.tar.gz: f9114f0b6e477796823feecd83633604ff1a1709e1f05805152e6baa191c58d7
+  metadata.gz: 8a9ad5e67ac6b9190c6faf6929a3596d17e672680c3ffe175bc3d31b78e7edb0
+  data.tar.gz: 7155ef205db9e0f79470674c2053f4194f35b7c61bce215b7e3ae499a9b56095
 SHA512:
-  metadata.gz: c04ed219d8587f3e0fbccc0d50c45fc2c920258b6f1a5f5672aa13e3af96b3eef2ef35e7ad6a8a2ff6518eaf3803a126957c1af3c69cacaed29d68d83b27a3a9
-  data.tar.gz: 8cbbf7d6e04a6c30fbec40df324b8a63ad1e31c3bbb85cc6cc51d8e1bdd1acd97956d423e164278c073cb5a9a58c86528327e8169d8533a6e727607caca88f0f
+  metadata.gz: 2a75f5eceb4659599ea3761e1fa620d21bead332de83528f3bef5fbc587275bb2fe43ce6cb37ea904205270d0bf9ff0345391b2a419e988c130c9dc1f7806237
+  data.tar.gz: 799c0ac7fd4d2a8a48e7b6dd07a40edf206788570b344ed2fdf0b1aad5bd5fbe5699f5e4f9645f3df09de5b2b59f99052974a1a343e4b77d676d06f94868c092

data/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 ## [Unreleased]
 
+## [0.3.1] - 2026-10-15
+
+### Engine: libhegel 0.45.7 (was 0.45.4)
+
+The [libhegel 0.45.7 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.7)
+describe 0.45.7 alone. The
+[engine changelog](https://github.com/hegeldev/hegel-rust/blob/libhegel-v0.45.7/hegel-c/CHANGELOG.md)
+describes each engine release after 0.45.4, up to 0.45.7.
+
+Each platform gem carries `libhegel` 0.45.7. The engine only adds to its C
+interface, and these bindings do not use the addition. A caller has nothing
+to change in code. The engine changes these messages for a caller:
+
+- `from_regex` with a pattern that no string matches, such as `"(?!)"`,
+  raises `Hegel::Error` with a message that names the pattern and says
+  that it `matches no string`. Before, the run raised `Hegel::Error` with
+  a message that starts with `Unsatisfiable`.
+- The FilterTooMuch health check message says how to suppress the check
+  with the `suppress_health_check` setting, and it says "rejected by
+  assume() or a filter". Before, it showed Rust syntax. The
+  `FailedHealthCheck:` and `Unsatisfiable` prefixes do not change.
+
 ## [0.3.0] - 2026-10-14
 
 ### Engine: libhegel 0.45.4 (was 0.45.1)
@@ -174,6 +196,7 @@ The engine is called through the `ffi` gem. Each platform gem carries the
 matching `libhegel` 0.32.5 build. The platform-independent gem carries none,
 so a run on it needs `HEGEL_LIBHEGEL_PATH` pointing at a local build.
 
+[0.3.1]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.3.1
 [0.3.0]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.3.0
 [0.2.1]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.2.1
 [0.2.0]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.2.0

data/lib/hegel/libhegel_version.rb

@@ -5,5 +5,5 @@ module Hegel
   # Hegel::VERSION (the gem's own release): hegel-go and hegel-typescript keep
   # the two separate too, so bumping the pinned engine can land as its own
   # commit without also releasing a new gem version.
-  LIBHEGEL_VERSION = "0.45.4"
+  LIBHEGEL_VERSION = "0.45.7"
 end

data/lib/hegel/runner.rb

@@ -178,9 +178,9 @@ module Hegel
     # Pulls test cases from +run+ until hegel_next_test_case reports none
     # left (a nil out-parameter, not an error). Never counts iterations
     # itself: test_cases bounds generation, not how many times shrinking
-    # and rejected cases call the body. Measured against libhegel 0.45.4, a
+    # and rejected cases call the body. Measured against libhegel 0.45.7, a
     # run configured for 20 test cases whose body rejected nearly every case
-    # took 475 to 1607 iterations. +stats+ does its own, different counting
+    # took 913 to 1818 iterations. +stats+ does its own, different counting
     # -- see GenerationStats above.
     def drive(impl, ctx, run, stats, captures, &block)
       loop do

data/lib/hegel/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Hegel
-  VERSION = "0.3.0"
+  VERSION = "0.3.1"
 end

data/skills/hegel-ruby/references/ruby/reference.md

@@ -494,12 +494,12 @@ expose) are not available in this binding; `codec:`, `min_codepoint:`, and
 `max_codepoint:` are the alphabet controls it exposes today.
 
 Other generators cover most character-set jobs. These results were measured
-with libhegel 0.45.4:
+with libhegel 0.45.7:
 
 | Job | Generator | Measured output |
 |---|---|---|
-| Characters to include | `from_regex("[ぁ-んA-Z0-9]{1,5}", fullmatch: true)` | `"0"`, `"ぢ3"`, `"るJこ"`; 30 draws all matched the pattern |
-| Characters to exclude | `from_regex("[^,\\t\\n]{0,6}", fullmatch: true)` | `""`, `"\u0010ùóR'<"`; 30 draws contained no comma, tab, or newline |
+| Characters to include | `from_regex("[ぁ-んA-Z0-9]{1,5}", fullmatch: true)` | `"0"`, `"お"`, `"Dぷぎ"`; 30 draws all matched the pattern |
+| Characters to exclude | `from_regex("[^,\\t\\n]{0,6}", fullmatch: true)` | `""`, `"âb¤"`; 30 draws contained no comma, tab, or newline |
 | A contiguous block | `text(min_codepoint: 0x300, max_codepoint: 0x36F)` | Every character of 100 draws was in U+0300 through U+036F |
 | An arbitrary alphabet | `arrays(sampled_from(%w[ß a İ]), max_size: 4).map(&:join)` | 30 draws, each built only from `ß`, `a`, and `İ` |
 
@@ -512,14 +512,13 @@ inputs and reported this health check:
 
 ```
 FailedHealthCheck: FilterTooMuch — it looks like this test is filtering out
-too many inputs. 50 inputs were filtered out by assume() while only 0 valid
-inputs were generated. If this is expected, suppress the check with
-suppress_health_check = [HealthCheck::FilterTooMuch].
+too many inputs. 50 inputs were rejected by assume() or a filter while only
+0 valid inputs were generated. If this is expected, suppress the
+FilterTooMuch health check with the suppress_health_check setting.
 ```
 
-The engine writes that last sentence in its own naming. This binding takes
-the same setting as `suppress_health_check: [:filter_too_much]`, listed in
-[Settings](#settings).
+This binding takes that setting as
+`suppress_health_check: [:filter_too_much]`, listed in [Settings](#settings).
 
 Unconfigured `text` draws from a much wider Unicode range. In 200 draws of
 `text(min_size: 1, max_size: 4)`, the results included emoji, private-use
@@ -745,6 +744,13 @@ translated): `from_regex(/[a-z]{3}/)` raises `Hegel::Error` at draw time,
 Regexp"`. Pass `my_regexp.source` explicitly for a pattern confirmed to
 need no flags and to use only syntax the two grammars share.
 
+A pattern that no string matches, such as `"(?!)"`, also raises
+`Hegel::Error` at draw time. The engine writes the message, and it names
+the pattern: `from_regex("(?!)")` raises
+`"HEGEL_E_INVALID_ARG (-5): regex pattern \"(?!)\" matches no string the
+generator can produce"`. Since libhegel 0.45.7 the engine makes this
+check.
+
 ### `emails`
 
 An RFC 5321/5322 email address `String`.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hegeltest
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
 platform: x86_64-linux
 authors:
 - meganemura