swiftlang/swift

No fix-it for escaping closure captures 'inout' parameter

Open

#87,830 建立於 2026年3月12日

在 GitHub 查看
 (3 留言) (0 反應) (1 負責人)Swift (69,989 star) (10,719 fork)batch import
SILcapture listsclosurescompilerdiagnostics qualityexpressionsfix-itsgood first issueinoutswift 6.3value capturing

描述

Description

No response

Reproduction

func bar(_: @escaping () -> Void) {}
func foo(_ i: inout Int) {
  bar {
    _ = i
  }
}

Expected behavior

An additional note asking if the user wants to capture a copy, with a fix-it to capture the parameter explicitly.

Environment

Swift version 6.3-dev (fefcb257b5b5d32)

Additional information

No response

貢獻者指南

技術棧
swift
領域
developer experiencetooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Swift language knowledgeCompiler development basicsUnderstanding of diagnostic system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the Swift compiler's diagnostic emission for inout captures in escaping closures. The fix it likely needs to be added in the Sema or TypeCheck pass. Look at existing fix its in the codebase, such as those in lib/Sema/TypeCheckClosures.cpp or lib/AST/DiagnosticSema. Check if the assignee has a branch or comments indicating progress. The expected behavior is to suggest capturing the parameter explicitly (e.g., `let copy = i`). Refer to similar fix its for reference.
No fix-it for escaping closure captures 'inout' parameter · swiftlang/swift#87830 | Good First Issue