jextract/jni: Protocol property setters reference an incorrectly named adapter

未关闭
#949 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
56/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
java, swift
领域
backend, tooling

调研方向

Start by tracing the generated JNI binding for a public protocol-typed property with Java callbacks enabled, comparing the wrapper declaration name with the setter argument conversion reference. Check the related protocol-parameter adapter issue #946 for nearby context. Done when property setters, label-disambiguated overloads, and Java keyword names generate matching adapter references and the resulting Swift compiles.

由索引模型根据 Issue 内容生成。

描述

Problem

With Java callbacks enabled, JNI bindings for a public protocol-typed property can generate a Swift setter that references a wrapper class under a different name from its declaration. The generated Swift code then fails to compile.

Example

public protocol Callback {
  func value() -> Int64
}

public final class Service {
  public var callback: any Callback

  public init(callback: some Callback) {
    self.callback = callback
  }

  public func read() -> Int64 {
    callback.value()
  }
}

The generated wrapper declaration uses the Swift property name, while the setter's argument conversion uses the Java setter name:

// Generated wrapper declaration
final class _Service_callback_newValue_Wrapper: SwiftJavaCallbackWrapper {
  // ...
}

// Generated setter argument conversion references
// _Service_setCallback_newValue_Wrapper instead.

The same kind of mismatch can occur when Java method names differ from Swift names for label-disambiguated overloads or Java keywords.

Related: #946 also concerns protocol-parameter adapters, but reports duplicate declarations for overloads.

Reference workaround implementation: https://github.com/qoncept/swift-java/pull/16

主要语言
Swift
星标
1.3k
派生
127
平均合并
2 天 14 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

swiftlang/swift-java 的其他 Issue

查看 swiftlang/swift-java 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。