Warning generated for `@dynamicMemberLookup`
Open
Nobody has claimed this yet.
fuse
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
When // SKIP @bridge is applied to a type with @dynamicMemberLookup, there is no way to silence that warning even if subscript(dynamicMember:) is not bridged
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
No file or test is named in the issue. Start by tracing handling of // SKIP @bridge for types marked @dynamicMemberLookup, then verify the behavior when subscript(dynamicMember:) is not bridged. Done means the warning can be silenced in that case without affecting other bridge warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100