Summary: | ASTParser.createASTs parses more CUs then required | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Benno Baumgartner <benno.baumgartner> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | dirk_baeumer, markus.kell.r, philippe_mulet |
Version: | 3.2 | ||
Target Milestone: | 3.2 M4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Benno Baumgartner
2005-11-03 11:16:28 EST
I believe it is indeed a consequence of the fix for bug 111822. Now, you need this in order to exploit DOM ASTs, if not you may see partial binding information in presence of references to the downstream AST (if they wouldn't have been fully resolved). Offering a setting is something we could explore. Philippe, what we don't understand is that fact that when the extra CUs are parsed when already processed ALL ASTs we requested. And I guess this behavior as a negative impact in "Infer Type Arguments" as well (for which we don't have a performance test ;-)). Changed CompilationUnitResolver#resolve(ICompilationUnit[], String[], ASTRequestor, ...) to stop processing units if all requested ASTs and all requested binding keys have been returned. Added regression test BatchASTCreationTests#test070(). Verified for 3.2 M4 using build I20051212-0010 |