swiftlang / swiftlang/swift-java
jextract: Handle _Concurrency.Task better
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
I think jextract needs to be aware of this type and we should have a lib type for it, including some future returning "awaitable" funcs for the Java side.
This is uncommon to return tasks rather than do asynchronous funcs, but it does happen sometimes.
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 by reviewing the jextract implementation and how it currently represents Swift concurrency types. Investigate _Concurrency.Task and the requested Java-side awaitable functions, then define the required generated library type and behavior. Done means Task-returning APIs are represented appropriately for Java callers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100