-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve JavacBindingResolver #909
Conversation
org.eclipse.jdt.core.javac/src/org/eclipse/jdt/core/dom/JavacCompilationUnitResolver.java
Outdated
Show resolved
Hide resolved
de42c03#diff-af030ac91c9fb35cb660aa9076bd04fcbfde2ebc73c583664b39293fc8475e3bR449-R455 doubles the speed of the resolve method. |
There are around 13 new failures, I think these are them:
|
These two tests are invalid argument exceptions thrown by javac: org.eclipse.jdt.core.tests.dom.ASTConverter18Test.testBug433879c I think they are worth investigating further, because perhaps we are passing in bad values to javac. The other failures appear to be changes in the number of errors reported by javac. I am less worried about those ones. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me. Thanks, Snjezana!
I was worried but debugging shows that now with this change, the UnusedTreeScanner is run although there are errors in enter instead of being interrupted earlier. I think it's a good thing. If it becomes bogus, we'll have to add a check before running |
Related to #755