New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate that self is only used in escaping closures and conflicts #59
Comments
Counterpart of #321 |
👍 |
Love this. It would make searching for ref-cycles quiet a bit easier... :-) |
I could find the "explicit_self" rule but I couldn't find the identifier for this one. Anyone could help me with finding it ? Thanks! |
Doesn't exist yet. If anyone would like to build this rule, please go ahead! |
Any update on this? |
This issue has been automatically marked as stale because it has not had any recent activity. Please comment to prevent this issue from being closed. Thank you for your contributions! |
Reopening, as there is still demand for this rule based on #3579 and prior comments on 2020. |
Would love to see that implemented. |
Any status update on this "implicit_self" rule inclusion? 🤔 Thanks |
bump - my team would find this rule to be super useful ❤️ |
Bumptiybumpbump. Any status updates on this issue? I think we all want it ❤️ |
Any updates on this? |
Has this been implemented already? I would love to have this rule in SwiftLint! |
hello, bump any updates on the concerns/challenges of implementing this? |
Bumpbumpbump part 2? |
I've implemented parts for this rule in #4911. As mentioned there, what's missing
Please have a look into the PR and let me know which other test cases you can think of, what I've missed or what doesn't work like the rule assumes! |
Closing this as completed. The remaining part "implicit |
Use of
self
should be limited to escaping closures and scopes in which other declarations conflict.The text was updated successfully, but these errors were encountered: