Jens Fischer

I guess this should probably be generalized to `RedundantParenthesesCheck`, which also detects cases like these: ``` haxe var i = (true) = 0 : 1; if ((object != null) &&...

That particular example should probably still error, because `$name` should be preferred over `${name}`.

Sounds good to me, I actually had something similar in mind! For the modes I'd suggest different names: `Before`, `After`, `Around` and `None`.

One question is whether the old whitespace checks should be removed when adding this (breaking change).

Seems like a good idea!

Both of that seems sensible. :)

Can't seem to reproduce this anymore.. Might've been an old hxparse version.

This fails on python (I've been playing around with checkstyle on the python and lua targets. Don't think there's any real use-case for that, but I found a few Haxe...

FWIW, I think forbidding anon functions in favor of short lambdas is a bad idea. There are some special cases where arrow functions don't work well due to their implied...

Hm, I guess it must be a Neko bug then. :/ Perhaps it's trying to run a regex over that long line and the regex engine can't handle strings that...