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

Abierto
  • ¿Algo no está bien?
#613 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C#
Estrellas
29
Forks
16
Merge medio
5 d 21 h
PR fusionados (30 d)
9

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sillsdev/machine

Todos los issues de sillsdev/machine

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.