jextract/jni: Expose Swift protocol requirement defaults to Java callbacks

未关闭
  • 哪里不对？
#948 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java, swift
领域
backend-api-design

调研方向

Start by reading #562 and #891, which describe related extension-member and compilation behavior, then inspect the JNI callback generation entry points in the repository. Determine how an unconditional Swift protocol extension implementation can remain the implementation while calls to other requirements dispatch to Java overrides; done means Java callbacks can inherit that default and the example works.

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

描述

Problem

JNI callback interfaces currently leave protocol requirements abstract even when Swift supplies an unconditional implementation in an extension. Java implementors must repeat that implementation instead of inheriting the Swift behavior.

Example

public protocol Greeter {
  func name() -> String
  func greeting() -> String
}

extension Greeter {
  public func greeting() -> String { "Hello, \(name())" }
}

With Java callbacks enabled, it would be useful for a Java implementation to provide only name() and inherit the Swift implementation of greeting():

Greeter greeter = () -> "World";
String message = greeter.greeting(); // "Hello, World"

The Swift body should remain the implementation, and its calls to other requirements should dispatch to the Java receiver, including any Java overrides.

This is related to #562, which discusses exposing extension members as Java default methods, and #891, which reports a compilation error when a protocol requirement has a default implementation.

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

主要语言
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 摘要。