skiptools / skiptools/skip-bridge
Type implementing protocol fails to bridge when `async throw` is missing
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 6
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The ActualFoo type here is correctly implementing Foo
protocol Foo {
func bar() async throws
}
class ActualFoo {
func bar() {}
}
But SkipBridge throws this error:
[✗] Class 'ActualFoo' is not abstract and does not implement abstract member 'bar'.
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 minimal Swift protocol and ActualFoo example in the issue and trace how SkipBridge handles async and throws protocol requirements. The fix is done when this implementation bridges without reporting that bar is missing.
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
- Clearly specified
- Newbie friendliness
- 45/100