Repository navigation
docs: SPEC for helper check propagation — the call path, not the body, decides - #338
Merged
Merged
Conversation
…, decides Direction confirmed by the user (2026-09-26, §9-71.6 F2): arithmetic executed on behalf of a fallible body is checked wherever it is written, and -3 propagates. The draft asks for DP-P2..P11: exported infallible callees included, any return type, fail at the operator, DP-O6 parity after `result`, one set in ir.rs read by codegen and both bindings (the prototype's .h/.pas never declared ML_ST_OVERFLOW for a helper-only path), `ml_ck_<f>` names (the prototype's name collided, E0428), emit referenced bodies only (the prototype broke builds under ambient -D warnings), fingerprint/ABI unchanged, no replacement escape hatch for DP-O7, and a helper added to an example for acceptance D. Measured before writing: a census through the compiler's IR (no corpus helper relies on intended wrap), code size, and the prototype's defects, three of them re-run by hand. Grok plan: exported callees YES, one set SUFFICIENT, referenced-only emission over allow. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ers, the re-measure is in scope, and non_snake_case stays out Grok verify: `fixed` is excluded because it is string-return only, not by DP-A3, and a fallible helper can produce -2 (already declared, every ! body is scanned); acceptance I had no scope item; an allow(non_snake_case) line would change every module's generated Rust and contradict acceptance H, so the pre-existing non_snake_case case is recorded in §5 instead, and acceptance G separates the collision check from the -D warnings row. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Owner
Author
🔵 SCAManager 분석 결과총점: 89/100 (등급 B) 점수 상세
|
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.
docs/slices/SPEC-helper-check-propagation.md초안. 방향은 사용자 확인(2026-09-26, §9-71.6의 권고안 F2) —!본문이 부른 무한 헬퍼의 산술도 검사하고-3을 전파한다. §4의 DP-P2~P11은 확인 대기이고 제품 코드는 없다. 관련: DP-O7(이 슬라이스가 뒤집는다) · DP-O4/O6/O8 · D17 · #238.쓰기 전에 잰 것 (E2)
!에서 닿고 17개가 검사할 연산을 가진다 · 의도한 wrap에 기대는 헬퍼는 어느 코퍼스에도 0 ·examples/에는 이 모양이 없다(수용 D는 예제에 헬퍼를 넣는다, DP-P11).-3을 선언하지 않음 · 쌍둥이 이름 충돌(E0428) · 주변-D warnings에서 빌드 실패 · 쓸모없는 쌍둥이 ·export가 검사를 멈춤. 셋(충돌 ·-D warnings· export)과 지문 불변 · 멈춤→-3은 손으로 다시 쟀다..text+9.7%.Grok
allow(dead_code)대신 참조되는 본문만 방출(과다 방출을 숨기지 않으려고 — 이 답이 설계를 바꿨다).-2는 무한 헬퍼에서만 없고fixed의 이유가 달랐다) ·ml_ck_이름 무충돌 CONFIRMED · 내부 일관성 DISCREPANCY(수용 I의 범위 항목이 없었고,allow(non_snake_case)가 모든 모듈의 생성 Rust를 바꿔 수용 H와 부딪혔다 → 이미 있던 문제라 §5로 옮김) → 고친 뒤 재검증 CONFIRMED.doc_claims50/50.🤖 Generated with Claude Code