Sugared Optional<()> return types (e.g. Void?) are caught by the redundant_void_return rule.
#1761
Labels
bug
Unexpected and reproducible misbehavior.
Comments
ryanbooker
changed the title
Optional<()> return types (e.g. Void?) are caught by the void_return rule.Optional<()> return types (e.g. Void?) are caught by the redundant_void_return rule.
ornithocoder
added a commit
to ornithocoder/personal-fork-swiftlint
that referenced
this issue
Aug 16, 2017
after changes introduced by realm#1761.
Merged
marcelofabri
pushed a commit
that referenced
this issue
Aug 17, 2017
after changes introduced by #1761.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
foo() -> ()andfoo() -> ()?are not the same type. The later is currently rejected byredundant_void_returnas being equivalent to the former.The text was updated successfully, but these errors were encountered: