Repository navigation
[sergo] Sergo Report: STABLE-84 Reconcile + ParenExpr Equality Gap - 2026-10-24 #71551
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-25T04:00:04.084Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
Tool Update
No Serena tool-list changes (24/24 stable). Language server status: ready, checked first this run.
Strategy Split (50/50)
Findings
mapdeletecheck: asymmetric ParenExpr wrapping escapes detection (filed)
pkg/linters/mapdeletecheck/mapdeletecheck.go sameExpr (lines 169-202) requires both sides of a comparison to already be a ParenExpr node before recursing into them, with no upfront UnwrapParenExpr call. This differs from the already-fixed reference pattern in uncheckedsliceindex.go (366-368), which unwraps both operands first. As a result, a parenthesized map key on only one side of the pattern (for example the if-condition key wrapped in parens but the delete() call argument not wrapped) silently escapes this CI-enforced, autofix-capable linter. Zero testdata coverage for any ParenExpr shape exists today. Filed with a concrete before/after recommendation and a validation checklist.
Verification sweeps (no new issue)
Generated Tasks
Issues Created
Metrics
Historical Context
This is the third consecutive run with a stable 84-linter registry. The standing day-one probes (paren_unwrap_gap, ci_target_asymmetry, idiom_reflag_no_allowlist, node_filter_too_narrow) are now waiting on either an 85th linter or a fresh shared-helper shape to probe. A repo-wide grep for the sameExpr(pass, x, y ast.Expr) bool signature found exactly 2 implementations; both are now solo-audited.
Next-Run Focus
References:
All reactions