HermitCrab synthesis: 98% of Mbugwe synthesis work goes to candidates whose root lookup hits but never match the surface
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
Start with docs/hermitcrab-2026-10-21-search-cost-round.md, lines 319–330, then review the failure-reason trace from #534 and the related discussion in #560. Identify where synthesis failures are traced and determine how to classify candidates whose lexical lookup hits but whose surface does not match. Done means the failures are classified by rejecting rule in work steps; do not add pruning.
索引モデルが issue の本文から書いたものです。
説明
Claude-drafted.
98% of Mbugwe's synthesis work goes to candidates whose lexical lookup hits but whose synthesis never matches the surface form. It is the largest unaddressed bucket on Mbugwe, and no sound prune is known. The same share was 86% on the private deletion variant, but that figure was measured before a port fix (fix B) that cut the variant's total work by 94.7%, so it does not describe the current port or hc.dll.
Status: open research lead, not started.
What we know (HC-Rust port, synthesis work in work steps):
- 98% on Mbugwe; the record does not give the sample or the fix state for that figure.
- 86% on the private deletion variant, before fix B (303,966,311 work steps then, 16,220,190 after).
- A lexical oracle cannot prune these candidates: the root is reachable, so lexical-reachability pruning (ledger rows 10 and 11) cannot reach them.
- The 2026-10-27 census on
hc.dllattributes steps by failure reason (SurfaceFormMismatchis 27.2% of Mbugwe synthesis steps) but does not split root-reachable failures.
Not known: which rules reject these candidates, and whether a sound condition exists.
Proposed change: classify these failures by the rule that rejects them, in work steps. Do not add a prune until a sound condition is found.
Related: #534 (PR, closed, not merged), #560 (open). The failure-reason trace that would do the classification is #534's; the census harness (branch research/failure-reason-stats at af97348b) is test-only. PanGloss: sillsdev/PanGloss#109 (pointer, open), which depends on sillsdev/PanGloss#34 (open, ports #534).
Next: revive the #534 failure-reason trace, or extend the census harness, and report work steps per rejecting rule on Mbugwe.
Evidence -- what the record states
- Open lead 4: 86% (deletion variant, before fix B) and 98% (Mbugwe) of synthesis work goes to candidates whose lookup hits but whose synthesis never matches the surface (L338-L341); the same sentence appears in the C1 verdict (L160-L162).
- Fix B: a re-inserted segment-class node keeps its members on a featureless grammar. It was a bug in the Rust port; C# was already exact. Deletion variant, held list: 303,966,311 to 16,220,190 work steps, 94.7% less (L51).
- Before fix B, a two-word profile of the deletion variant put synthesis at about 90% of parser work (L101-L103).
Sources -- pinned to 2eba2f50 (closed PR #490 record)
- Search-cost round, open lead 4, L338-L341.
- Census by failure reason: synthesis round L96-L150; ledger row 31, L152; rows 10 and 11: L95-L96.
What would reopen this
A sound condition that rejects a root-reachable failure class before it is synthesised, with a work-step ceiling worth its cost.
- 主要言語
- C#
- スター
- 29
- フォーク
- 16
- 平均マージ
- 5日 21時間
- マージ済み PR(30日)
- 9
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
sillsdev/machine のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 62/100
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 15/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 28/100
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
メンテナーはふだん 1 日以内に返信
sillsdev/machine の issue をすべて見る
似ている issue
-
effort:S P3 refactor
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
nightscout/nocturne#3243 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
dasher-project/Dasher-Windows#84 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
libnativeapi/nativeapi#21 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 3 日以内に返信
-
enhancement P3 performance
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
thomhurst/TUnit#7380 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信