hegeltest 0.2.1-aarch64-linux → 0.3.1-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: aaeb9d0de3eed73e101255a9737dcd411e7819dfd559b9b6654556563bd1a9ab
-  data.tar.gz: 1a8b52232cc7ea3b746c4224b5a16aebd910405a0b6a8403e067a23ce175ad6b
+  metadata.gz: d0372fb8bf6fc7928f6c0790df8b89c47ba5b705c823cc9133d950bb894fb840
+  data.tar.gz: 9db269f1bbd5c2dd97c41e9eaa23a633732f3ffb5b190825b970523b1d7b2a4c
 SHA512:
-  metadata.gz: 15fd917172691c48b448ba688ca00fae54cea30bf67408a4f34f96a09a95d37564e8c6cfb90eaf7e2dc68adf4d2285d8f6f3315e771a0838d7cf9e2f8fb0d2e4
-  data.tar.gz: 28c4f53b9dfeedf865f266940a27e8d012604bb4c32c3fc63d2db5af9af48449d08a933e24e2017d6a726512653b714c7c88bcacb55afe928cd8d5ea2e04ba29
+  metadata.gz: 4f7bc4b5b69bfbbcf7802a8b5f24e5c3535e2f2074e5112c86c73876d1f445dbc520d18ad907c08f9a6c862392464f18c660194f790a502c3f4f824d5131c187
+  data.tar.gz: 175551928ce3681380f273d2cb3d39ac8787a6fd7b4249ef4f92a2c4bd3f8ffbf39b4080377354eb184b5f9389405d41045515701477a168f87ce83316f59049

data/CHANGELOG.md

@@ -2,23 +2,91 @@
 
 ## [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)
+
+The [libhegel 0.45.4 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.4)
+describe 0.45.4 alone. The
+[engine changelog](https://github.com/hegeldev/hegel-rust/blob/libhegel-v0.45.4/hegel-c/CHANGELOG.md)
+describes each engine release after 0.45.1, up to 0.45.4.
+
+Each platform gem carries `libhegel` 0.45.4. The engine only adds to its C
+interface, and these bindings do not use the additions. The engine
+changes these results for a caller:
+
+- A run that generates no valid test case now raises `Hegel::Error` with a
+  message that starts with `Unsatisfiable`, also when
+  `suppress_health_check:` holds `:filter_too_much` or
+  `:test_cases_too_large`. Before, such a run passed. A test that rejects
+  every case and expects to pass must now draw at least one valid case.
+- `from_regex` records each drawn string as one choice that the pattern
+  constrains. A failure shrinks inside the pattern, so
+  `from_regex("(?:bbbb|a)", fullmatch: true)` now shrinks to `"a"`, where
+  it stopped at `"bbbb"` before. The example database drops a failure that
+  an earlier engine saved for a `from_regex` draw, so the first run after
+  the update does not replay it.
+- `from_regex` rejects a look-behind of variable width, such as
+  `(?<=a*)b`, with `Hegel::Error`, as Python's `re` does.
+- `\w`, `\d`, `\s`, and case-insensitive matching in `from_regex` follow
+  Unicode 17.0. Before, they followed Unicode 15.1.
+- A run stops when its test-case budget or its budget of invalid cases is
+  spent. Before, it could also stop after ten rejected cases in a row that
+  it had seen before.
+
 ## [0.2.1] - 2026-10-08
 
-Each platform gem carries `libhegel` 0.45.1, up from 0.45.0. A caller has
-nothing to change. The engine now reads a NULL string buffer with length
-zero as the empty string, and it rejects a NULL buffer with a nonzero
-length. These bindings send neither case, so a drawn value does not
-change: `from_regex("", fullmatch: true)` draws `""` on both engines.
+### Engine: libhegel 0.45.1 (was 0.45.0)
+
+The [libhegel 0.45.1 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.1)
+describe the engine changes.
+
+Each platform gem carries `libhegel` 0.45.1. A caller has nothing to
+change. The engine now reads a NULL string buffer with length zero as the
+empty string, and it rejects a NULL buffer with a nonzero length. These
+bindings send neither case, so a drawn value does not change:
+`from_regex("", fullmatch: true)` draws `""` on both engines.
 
 ## [0.2.0] - 2026-10-07
 
+### Engine: libhegel 0.45.0 (was 0.32.5)
+
+The [libhegel 0.45.0 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.0)
+describe 0.45.0 alone. The
+[engine changelog](https://github.com/hegeldev/hegel-rust/blob/libhegel-v0.45.0/hegel-c/CHANGELOG.md)
+describes each engine release after 0.32.5, up to 0.45.0.
+
+Each platform gem carries `libhegel` 0.45.0. The engine changed its C
+interface in several places between the two, and these bindings follow
+each change. The sections below list what that changes for a caller.
+
+### Ruby
+
 The floor is Ruby 3.4. A project on Ruby 3.3 stays on 0.1.1. See
 [ADR 0017](docs/adr/0017-raise-the-ruby-floor-to-3-4.md).
 
-Each platform gem carries `libhegel` 0.45.0, up from 0.32.5. The engine
-changed its C interface in several places between the two, and these
-bindings follow each change.
-
 ### Changes a caller has to make
 
 `Hegel.test` no longer takes `stateful_step_count:`. Pass `step_count:` to
@@ -128,6 +196,8 @@ 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
 [0.1.1]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.1.1

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.1"
+  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.0, 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 1040 to 1537 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.2.1"
+  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.0:
+with libhegel 0.45.7:
 
 | Job | Generator | Measured output |
 |---|---|---|
-| Characters to include | `from_regex("[ぁ-んA-Z0-9]{1,5}", fullmatch: true)` | `"ぁ"`, `"Hわ9ごう"`; 30 draws all matched the pattern |
-| Characters to exclude | `from_regex("[^,\\t\\n]{0,6}", fullmatch: true)` | `""`, `"\u008FBՔ\u0014੐C"`; 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`.
@@ -1219,11 +1225,18 @@ value already in the shape you need):
 
 ```ruby
 result = Hegel.test(test_cases: 20, suppress_health_check: [:filter_too_much], verbosity: :quiet) do |tc|
-  tc.draw(integers.filter { |_n| false })
+  tc.draw(integers(min_value: 0, max_value: 1_000_000).filter(&:zero?))
 end
 result # => nil
 ```
 
+The suppressed check does not let a run pass with no valid input. A
+predicate that never holds, such as `integers.filter { |_n| false }`,
+still raises `Hegel::Error`, with a message that starts with
+`"Unsatisfiable: unable to satisfy the test's assumptions."` Since libhegel
+0.45.2, the engine ends every run that generates no valid test case this
+way.
+
 ## Gotchas
 
 1. **Float defaults include NaN and infinity when unbounded.** `floats` with

metadata

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