HermitCrab conformance: producible behaviour has no discriminating fixture after the non-producible retirement

Geschlossen
  • Stimmt etwas nicht?
#613 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
csharp
Bereich
testing-qa

Rechercherichtung

Start with the conformance fixtures named in the issue, especially bantu-tam-fusion and suffixing-evidential-adjacency-chain, and the test for NonPartialRuleProhibitedAfterFinalTemplate. Check the self-check and HCLoader to see which gaps are real. Done means each listed gap has a producible grammar that fails when its behaviour regresses, and conformance/docs/what-it-claims.md matches the 127-fixture corpus.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Retiring the non-producible fixtures left FieldWorks-producible behaviour with no discriminating fixture. A regression in these paths would pass the conformance suite. The self-check still reports 137 of 137 runs passing at e9569ec0, so nothing there shows the gap.

Status: open. Each gap needs a producible grammar, never a revived engine-only fixture.

What we know (most important first):

  • NonPartialRuleProhibitedAfterFinalTemplate is NotEvidenced for both arms: the same-word evidence relied on isCliticRule, and its severance list still names that attribute.
  • MaxApplicationCount has never been exercised from a producible grammar.
  • MPR features on phonological subrules and the StemName junction lost their dataflow cells.
  • bantu-tam-fusion (#578) tests no fusion. All 200 rules put a plain subrule first, which matches any stem, so the fusion subrule is never reached. Deleting all 200 changes none of the 60 results.
  • suffixing-evidential-adjacency-chain no longer separates "somewhere" from "adjacent" scope for its exclusions.

Not known: which of these FieldWorks users reach in practice.

Proposed change: one small witness per gap, ranked as above. Give bantu-tam-fusion subrules that can reach fusion, with constrained plain subrules. Add separating words to the evidential chain. New rows come from the engine and are reviewed against the rules.

Related: #480 (open), #578 (open), #505 (open).

Next: write a producible witness for NonPartialRuleProhibitedAfterFinalTemplate.

Smaller items
  • Six new open gap-baseline rows: MetathesisRule/multipleApplicationOrder/rightToLeftIterative, MorphologicalPhonologicalRuleFeatureGroup/matchType/all and /any, .../outputType/overwrite, Stratum/morphologicalRuleOrder/linear, and ordering:edge-cases/optional-template-composite/slots/t2pfx~t2mandatory. Check each for producibility first: linear and the feature-group settings may need no witness.
  • redupMorphType suffix: only prefix remains. ExcludedEnvironments was at risk: confirm that a witness remains.
  • isActive="no" on templates, phonological rules and metathesis rules: confirm what HCLoader does before treating it as a gap.
  • The mutant stack-overflow path is tested only at its classification. The real overflow reproduced only on a deleted fixture.
  • The two deleted MPR stress fixtures were the benchmark for closed PR #570. An inflection-class benchmark could be rebuilt on inflClasses.
  • conformance/docs/what-it-claims.md narrative figures predate the 127-fixture corpus.
  • FieldWorksWitnessDirectoriesAreShapedCorrectly has no size or element check for minimal LDML.

🤖 Generated with Claude Code

Vorherrschende Sprache
C#
Sterne
29
Forks
16
Ø Merge
5 T. 20 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sillsdev/machine

Alle Issues in sillsdev/machine

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.