swiftlang / swiftlang/swift-java
jextract: make sure and formalize we handle overloads properly
Open
Nobody has claimed this yet.
feature:jextract
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
This may be more of a documentation task, unless we find bugs. We should document how overloads in the generated Java correspond to the Swift side.
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 jextract's handling of overloads and comparing the generated Java with the corresponding Swift declarations. Document how overloads map between the two sides, and record any behavior that appears incorrect for follow-up. Done means the overload correspondence is clearly explained and potential bugs are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100