Rules `explicit_self` and `unused_import` interfere with each other
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- Updated SwiftLint to the latest version
- I searched for existing GitHub issues
Describe the bug
I'm running swiftlint analyze with rules explicit_self and unused_import enabled in my project: https://github.com/gereons/SwiftLintBug1 (use the enclosed lint.sh to reproduce).
Expected result: swiftlint consistently reports the violations in all ten runs
Actual results vary. Most runs report Could not get cursor info twice, and find no violations. Some runs report Could not get cursor info once, and find explicit_self violations in one file. Rare runs do not report Could not get cursor info at all and correctly find violations in two files.
When either of the analyzer rules is commented out in the .yml, the remaining rule works correctly.
Swiftlint version: 0.38.1, installed via homebrew
Xcode version: 11.3
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 running the enclosed lint.sh from the linked SwiftLintBug1 reproduction with explicit_self and unused_import enabled, then compare repeated swiftlint analyze runs. Inspect the project’s .yml configuration and analyzer rule entry points to isolate their interaction. Done means both rules consistently report their violations without Could not get cursor info errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100