Danny Mösch

That's a major pain point that has been brought up in multiple issues already. Performance degrades when include/exclude paths containing wildcards are used in the configuration. The current implementation in...

> Any advancements in solving the time linting issue when using wildcard in path? It ruins the performance exponentially. > > > > ``` > > excluded: > > -...

For enum cases with associated values of type `Void` it's allowed to keep the empty parentheses. That's impossible to know on syntax-level. So we have to accept false positives -...

The Swift compiler now complains about empty parentheses on enum cases if the they don't have associated values. Therefore, `empty_enum_arguments` should just ignore them and only remove argument lists containing...

I think these steps are already covered by [this section](https://github.com/realm/SwiftLint#working-with-multiple-swift-versions), aren't they?

`xcode-select` isn't something specific for SwiftLint. It's the common way to switch between Xcode toolchains. Thus, we don't need to explain. The section I mentioned definitely relates to it. The...

> Very good. Is these environment variables specified in the docs? If not would it be wise to specify? Yes, they are [here](https://github.com/realm/SwiftLint#working-with-multiple-swift-versions).

> In the section titled "working with multiple swift versions"? Yes.

> After all this is a tool to make higher quality code and one aspect is that code be simplified and easier to understand, right? Yes, and one aspect of...

> > I like the proposed change. However, we have to be very careful with this change. It might break people's workflows. > > Absolutely. If someone is inadvertently passing...