Danny Mösch

So I restricted the rule to known standard functions by default and there is an option to enable it for all other closures as well. I actually doubt that anyone...

> In SwiftLint, there has only been one rewrite that caused a compile error afterwards - unfortunately one that SwiftLint cannot recognize as a false positive due to missing type...

> > @mildm8nnered: I'd like to hear your opinion. The rule doesn't seem to be so involved. Any more cases or shortcomings you can think of? > > Just trying...

> > > > @mildm8nnered: I'd like to hear your opinion. The rule doesn't seem to be so involved. Any more cases or shortcomings you can think of? > >...

While `.build` would be a good candidate to be ignored by default, I'm actually not inclined to hard-code certain folders into SwiftLint and maintain them. Other build tools have other...

The logic to include and/or exclude files is already pretty complicated and a critical area with respect to performance issues. Sorry, but I really don't want to make things worse...

> I’m a bit torn on this one. This is trading a fairly simple dependency for a considerably more complex one from a build system point of view. > >...

What about the `main` functions? Can they be removed/replaced?