Is it possible to have a warning for use of reserved Objective-C names (such as `description` or `debugDescription`)?
Open
Nobody has claimed this yet.
question
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
Pretty much all it title, Swift allows to use those names for methods and properties, but it makes use of interfaces like CustomStringConvertable impossible
I want to know how bad it already is in existing project and maybe prevent such conflicts in future.
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 files, tests, or entry points are named. Start by identifying how SwiftLint defines and tests warning rules, then determine the intended Objective-C reserved-name set and whether existing Swift code would trigger it. Done means a clearly scoped warning behavior, documented configuration, and tests covering the listed names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100