I don't believe so, but it would be a great addition to a dev toolkit. I know there's a version for flex (
flexpmd) that is based on the java
pmd. That seems like the most polished linter that is closest to Haxe syntax.
The compiler already does a number of sensible things for cleaning up unused methods, variables, etc. in code using the --dead-code-elimination flag. But, it would be nice to have the same power to clean up the actual code, instead of just the compiled output.
Some linting jobs are easy enough to implement with basic text processing (unused imports), but others are going to require syntax/scope-level awareness. Since the Haxe syntax is fairly complicated (macros, @:keep, etc.), this is going to be difficult.
Finally, linters are often "opinionated" in terms of what the author thinks code should look like. The best example of this is jslint. I won't link to the discussions on it, they're not hard to find. So, the more optional flags/configs for lint checking, the better imho.
-Justin