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

Sugared `Optional<()>` return types (e.g. Void?) are caught by the `redundant_void_return` rule. #1761

Closed
ryanbooker opened this Issue Aug 10, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@ryanbooker
Contributor

ryanbooker commented Aug 10, 2017

foo() -> () and foo() -> ()? are not the same type. The later is currently rejected by redundant_void_return as being equivalent to the former.

@ryanbooker ryanbooker changed the title from Sugared `Optional<()>` return types (e.g. Void?) are caught by the `void_return` rule. to Sugared `Optional<()>` return types (e.g. Void?) are caught by the `redundant_void_return` rule. Aug 10, 2017

@marcelofabri marcelofabri added the bug label Aug 10, 2017

ornithocoder added a commit to ornithocoder/personal-fork-swiftlint that referenced this issue Aug 16, 2017

Update Rules.md
after changes introduced by realm#1761.

marcelofabri added a commit that referenced this issue Aug 17, 2017

Update Rules.md
after changes introduced by #1761.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment