swiftlang / swiftlang/swift-java
jextract: closures with @Sendable should keep this information in generated java "closure" type
Open
Nobody has claimed this yet.
bug
feature:jextract
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
public func onEvent(_ f: @escaping @Sendable (Int64) -> Void) {}
Should generate a class onEvent_f @FunctionalInterface that we mark as @ThreadSafe
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the jextract handling for Swift closures and the generated Java closure type. Trace how @Sendable information is currently represented for onEvent and its onEvent_f type. Done means an @escaping @Sendable closure generates an @FunctionalInterface marked @ThreadSafe, with coverage for the example signature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100