shexjs / shex.js

75%

push

github

examples: splits and ambiguous demonstrate ThreadedMaterializer threading

Both share card-schema.shex, whose OneOf forks one NFA thread per
disjunct as the binding tree is consumed:

- splits (contact-Ann.ttl): no :tel binding, so the card:phone thread
  dies -- shexmap-debug shows the fork, the "branch died: no binding
  for :tel" event, and the single surviving card:mbox thread (plus the
  never-bound :tel warning on completion).
- ambiguous (contact-Bob.ttl): both :tel and :email are bound, so both
  disjunct threads are viable to the end and the materialization is
  ambiguous; the greedy scheduler accepts the first disjunct
  (card:phone), never exploring the equally-viable card:mbox thread
  (doc/threaded-materializer.md "Scheduling and acceptance").

splits is marked threadedOnly in the manifest: the legacy materializer
emits an empty graph for it (it can't recover from the dead disjunct),
so Map-test now checks just the validation->bindings half of
threadedOnly entries and leaves their materialization to
ThreadedMaterializer-test, which drives every manifest entry.
ambiguous passes both engines and stays fully covered.  5086 passing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2472 of 3892 branches covered (63.51%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

5642 of 6967 relevant lines covered (80.98%)

6395.71 hits per line