Static Analysis Tooling / Effective D

[Volcz]

On Tuesday, 21 January 2014 at 04:34:57 UTC, Brian Schott wrote:
> I've checked in code to the DScanner project that gives it some 
> basic static analysis capabilities. When run with the 
> --styleCheck option, it will warn about a few things like empty 
> declarations, implicit string concatenation, classes with 
> lowercase_names, catching "Exception", and a few other things.
>
> There's a small feature wishlist in the project's README, but 
> I'd like to get some opinions from the newsgroup: What kinds of 
> errors have you seen in your code that you think a static 
> analysis tool could help with?

I don't have any D specific errors that I keep repeating. I use 
SonarQube at work with Java. Here is a list of some of the 
"rules" that I use:
https://github.com/SonarSource/sonar-java/tree/master/java-checks/src/main/java/org/sonar/java/checks