Skip to content
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

empty_count still throwing false positives #1657

Closed
gwsounddsg opened this issue Jul 4, 2017 · 3 comments
Closed

empty_count still throwing false positives #1657

gwsounddsg opened this issue Jul 4, 2017 · 3 comments
Labels
duplicate Issues that already exist in other terms.

Comments

@gwsounddsg
Copy link

issue #1622 closed this exact issue and was updated in v0.20 but false positives are still happening. Here's an example:

mutating func set(outputCount count: Int) throws {
        try check(count)
        if count == 0 { // empty_count error
                throw AveModelErr.MixerStack_badOutput(count)
        }
}
@marcelofabri marcelofabri added the duplicate Issues that already exist in other terms. label Jul 4, 2017
@marcelofabri
Copy link
Collaborator

This is not the same issue as #1622, it's a duplicate of #827.

@gwsounddsg
Copy link
Author

@marcelofabri could you elaborate on how this is not the same as #1622? In the example code I showed swiftlint is throwing an empty_count error.

@marcelofabri
Copy link
Collaborator

#1622 is about words ending with count, such as discount. Please take a look at #827 for more discussion about your case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues that already exist in other terms.
Projects
None yet
Development

No branches or pull requests

2 participants