What does HackerNews think of error-prone?
Catch common Java mistakes as compile-time errors
Language:
Java
#27
in
Java
Big tech uses static analyzers a lot. See for example, these projects:
- https://fbinfer.com/ (<- This one was a breakthrough in static analysis in its time)
- https://github.com/google/error-prone
- https://github.com/facebook/SPARTA
And many others
For some of this stuff, there are compiler extensions that allow extra type checking to be added e.g. Google Error-Prone: https://github.com/google/error-prone with stuff like: https://errorprone.info/bugpattern/ReturnMissingNullable.
Doesn't help you with third party libraries, but across an org applying that rule (and others!) typically ensures some consistency.
Error Prone is not internal: https://github.com/google/error-prone
Google error-prone is a good alternative to FindBugs:
https://github.com/google/error-prone
http://errorprone.info/bugpatterns
Pros:
* has faster cycle times and integrates into compilation workflow
* emits fewer false positives
* active maintainers fix issues
* releases several times per year
Cons: * FindBugs has a greater breadth of checks
* current error-prone releases only work with Java 8