Bug 261315 - [content assist] Should also consider constructors in LRU cache
Summary: [content assist] Should also consider constructors in LRU cache
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: fix candidate
Keywords:
: 340795 393822 (view as bug list)
Depends on: 277691
Blocks: 387984
  Show dependency tree
 
Reported: 2009-01-16 03:55 EST by Dani Megert CLA
Modified: 2013-11-20 06:07 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2009-01-16 03:55:41 EST 
Once bug 6930 is fixed our LRU cache for types becomes less used in case like:
  new <code assist>
because now we'll get constructor proposals and not type proposals. Therefore we should consider extending the LRU cache on constructors.
Comment 1 Dani Megert CLA 2011-04-12 05:35:04 EDT 
*** Bug 340795 has been marked as a duplicate of this bug. ***
Comment 2 Dani Megert CLA 2012-08-27 06:50:57 EDT 
*** Bug 387984 has been marked as a duplicate of this bug. ***
Comment 3 Deepak Azad CLA 2012-11-07 17:20:47 EST 
*** Bug 393822 has been marked as a duplicate of this bug. ***
Comment 4 Markus Keller CLA 2012-11-09 09:34:07 EST 
Note that the basic problem is bug 277691 (missing boosting of assignable types). LRU boosting should only be a secondary measure on top of the base relevance.

To those who requested not offering types that don't match the context at all: We won't do that, since the user may want to use a chained method invocation, e.g. completing
    	Process p = new Pro|
to
    	Process p = new ProcessBuilder(args).start();