Rule Request: `explicit_return`
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 19.7k
- Forks
- 2.3k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
New rule request
explicit_return would check that the return is always present.
Description
I've found a rule for hiding return where is no needed https://realm.github.io/SwiftLint/implicit_return.html and a discussion about new rule about checking that the return exist https://github.com/realm/SwiftLint/issues/3632.
There is a discussion about that removing return is confusing and make it slow to reed a code. https://forums.swift.org/t/how-is-se-0255-implicit-returns-not-a-violation-of-swifts-design-principles/29267
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 reading the linked implicit_return rule documentation, issue #3632, and the Swift Forums discussion to define when an explicit return must be required. The issue does not name implementation files or tests, so clarify the rule's scope and expected violations before locating the relevant SwiftLint rule entry point and adding coverage.
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
- Needs clarification
- Newbie friendliness
- 25/100