swiftlang / swiftlang/swift-java
JNIExtract can't handle type-name/module-name conflicts
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
If the swift package's name is the same as a contained type, the type's Java interface isn't properly generated.
Needs more precise investigation.
Placeholder for now.
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 at the JNIExtract entry point and reproduce the case where the Swift package name matches a contained type. Trace why the type's Java interface is not generated, then confirm that the conflict case produces the expected interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100