Summary: | Search could be optimized based on visibility | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Peter Burka <peter_burka> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | akiezun, n.a.edgar |
Version: | 2.0 | ||
Target Milestone: | 2.1 M1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Peter Burka
2002-07-24 18:48:20 EDT
Indeed. Currently, search is able to find appropriate matches in incorrect code as well, and this is a nice feature which we want to preserve. Therefore, private methods may be referenced (incorrectly) from the outside, which means we have to look for them. If Java tooling only had to deal with correct code, things could be so much simpler... Closing. *** Bug 16176 has been marked as a duplicate of this bug. *** Could we search the current file and files with errors? (And probably files which haven't been built, too). That would still narrow down the search significantly. |