-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 implicitly unwrapped optionals #56
Comments
+1 for this |
I don't agree, they are quite useful |
If crashing is ok in your product, then yes they are useful. If management yells at you if you have crashes then they aren't ok... |
@frederic-adda It would just be an option to turn on. You'd be free to keep it off, of course. |
To clarify, implicitly unwrapped optionals certainly have their place, but using them superfluously is certainly a code smell that might indicate that the code should be refactored to avoid them. If a SwiftLint rule would apply 100% of the time, it should go in the Swift compiler. A linter exists to help identify code smells, not things that are incorrect 100% of the time. That's the language's job. |
Fixed on #1362 💥 |
Implicitly unwrapped optionals should not be used.
The text was updated successfully, but these errors were encountered: