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.