Static protocol requirements not bridged
Open
Nobody has claimed this yet.
fuse
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
Having a protocol with a static requirement fails to compile as the Skip plugin cannot generate a Kotlin bridging for it.
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 reproducing the compile failure with a Swift protocol containing a static requirement, then inspect the Skip plugin's Kotlin bridging generation. Done means the protocol compiles successfully and its static requirement is bridged to Kotlin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, swift
- Domain
- compilers, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100