Skip to content
This repository was archived by the owner on Feb 22, 2018. It is now read-only.

some analyzer errors are not reported #25

Closed
sigmundch opened this issue Jan 15, 2015 · 3 comments
Closed

some analyzer errors are not reported #25

sigmundch opened this issue Jan 15, 2015 · 3 comments

Comments

@sigmundch
Copy link
Contributor

For example, this error is not reported by ddc, but reported when invoking the analyzer from the command line:

abstract class B {
  m();
}
class A implements B {}

The analyzer indicates that A should be abstract or implement m.

@jmesserly
Copy link
Contributor

fwiw, I checked yesterday and this still reproduces. Very strange.

@jmesserly jmesserly self-assigned this Jun 11, 2015
@jmesserly
Copy link
Contributor

aha. We're not getting errors from ErrorVerifier:

/**
 * A visitor used to traverse an AST structure looking for additional errors and
 * warnings not covered by the parser and resolver.
 */
class ErrorVerifier extends RecursiveAstVisitor<Object> {

fwiw, that description sounds a lot like another visitor we have: CodeChecker!

@jmesserly
Copy link
Contributor

yeah, it turns out very many errors/warnings/hints were not reported. wow. https://codereview.chromium.org/1183733004/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants