Summary: | [1.5][compiler] Method lookup improvements | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Philipe Mulet
2005-07-05 10:39:56 EDT
Some stats to keep in mind (using standard source libs): - less than 1 in 5 implicit message sends need lookups (81% are exact matches) - same with non-implicit messages sends (82% are exact matches) - 36% of message sends are implicit So less than 1 in 5 message sends would benefit from any kind of caching Agreed. Maybe it should only do caching on generic method invocations, since these are quite expensive to compute. Also it would give us identity for generic method binding invocations, which we have as a feature request (for DOM AST side). I sorted fields and methods, to enable binary searching them. Canonicalized generic method bindings. Still inference is required, and could be optimized. post 3.2 As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |