fix(parser): remove 16 dead precedence declarations [#215 family F]#217
Merged
Conversation
Menhir emitted 16 "precedence level / %prec ... never useful"
warnings — declarations that never resolve any conflict because the
expression cascade disambiguates structurally. They are pure noise
that, alongside the conflict warnings, make a healthy build look
broken.
Removed (all certified "never useful" by Menhir itself):
- precedence level: `%right EQ PLUSEQ MINUSEQ STAREQ SLASHEQ`
(assignment ops — handled at statement level, never in the
expr operator cascade)
- precedence level: `%right BANG TILDE UMINUS UREF UDEREF`
(unary level — `expr_unary` is right-recursive and already
unambiguous)
- precedence level: `%left DOT LBRACKET LPAREN`
(postfix level — `expr_postfix` disambiguates structurally)
- the three now-orphaned `%prec UMINUS/UREF/UDEREF` on the unary
rules (UMINUS/UREF/UDEREF were pseudo-tokens used only there)
Provably parse-behaviour-neutral — removing a declaration Menhir
certifies resolves nothing cannot change any resolution. Verified:
- 16 "never useful" warnings: gone (0 remain)
- conflict counts UNCHANGED: 72 S/R, 10 R/R, 23 S/R states,
4 R/R states (identical resolution profile)
- `dune test --force` green at 257/257
The retained `LOWEST_TYPE_ARROW`/`ARROW` levels (#216, family A) are
*not* flagged — they do real work.
Refs #215
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 18, 2026
🔍 Hypatia Security ScanFindings: 44 issues detected
View findings[
{
"reason": "Stray AI.a2ml in root -- use 0-AI-MANIFEST.a2ml only",
"type": "banned",
"file": "AI.a2ml",
"action": "delete",
"rule_module": "root_hygiene",
"severity": "high"
},
{
"reason": "Superseded by 0-AI-MANIFEST.a2ml",
"type": "banned",
"file": "AI.djot",
"action": "delete",
"rule_module": "root_hygiene",
"severity": "high"
},
{
"reason": "Issue in quality.yml",
"type": "missing_workflow",
"file": "quality.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in security-policy.yml",
"type": "missing_workflow",
"file": "security-policy.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Action hyperpolymath/standards/.github/workflows/governance-reusable.yml@main needs attention",
"type": "unpinned_action",
"file": "governance.yml",
"action": "pin_sha",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "TypeScript file detected -- banned language",
"type": "banned_language_file",
"file": "/home/runner/work/affinescript/affinescript/affinescript-deno-test/example/smoke_driver.ts",
"action": "flag",
"rule_module": "cicd_rules",
"severity": "critical"
},
{
"reason": "TypeScript file detected -- banned language",
"type": "banned_language_file",
"file": "/home/runner/work/affinescript/affinescript/affinescript-deno-test/cli.ts",
"action": "flag",
"rule_module": "cicd_rules",
"severity": "critical"
},
{
"reason": "TypeScript file detected -- banned language",
"type": "banned_language_file",
"file": "/home/runner/work/affinescript/affinescript/affinescript-deno-test/mod.ts",
"action": "flag",
"rule_module": "cicd_rules",
"severity": "critical"
},
{
"reason": "TypeScript file detected -- banned language",
"type": "banned_language_file",
"file": "/home/runner/work/affinescript/affinescript/affinescript-deno-test/lib/compile.ts",
"action": "flag",
"rule_module": "cicd_rules",
"severity": "critical"
},
{
"reason": "TypeScript file detected -- banned language",
"type": "banned_language_file",
"file": "/home/runner/work/affinescript/affinescript/affinescript-deno-test/lib/runner.ts",
"action": "flag",
"rule_module": "cicd_rules",
"severity": "critical"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix(parser): remove dead precedence declarations [#215 family F]
Menhir emitted 16 "precedence level / %prec ... never useful"
warnings — declarations that never resolve any conflict because the
expression cascade disambiguates structurally. They are pure noise
that, alongside the conflict warnings, make a healthy build look
broken.
Removed (all certified "never useful" by Menhir itself):
%right EQ PLUSEQ MINUSEQ STAREQ SLASHEQ(assignment ops — handled at statement level, never in the
expr operator cascade)
%right BANG TILDE UMINUS UREF UDEREF(unary level —
expr_unaryis right-recursive and alreadyunambiguous)
%left DOT LBRACKET LPAREN(postfix level —
expr_postfixdisambiguates structurally)%prec UMINUS/UREF/UDEREFon the unaryrules (UMINUS/UREF/UDEREF were pseudo-tokens used only there)
Provably parse-behaviour-neutral — removing a declaration Menhir
certifies resolves nothing cannot change any resolution. Verified:
4 R/R states (identical resolution profile)
dune test --forcegreen at 257/257The retained
LOWEST_TYPE_ARROW/ARROWlevels (#216, family A) arenot flagged — they do real work.
Refs #215
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com