Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Recommenders/Attic/New and Noteworthy/0.1"
m |
m |
||
| Line 3: | Line 3: | ||
== Completion on Declared Variables == | == Completion on Declared Variables == | ||
| − | [[Image:Recommenders-completion-on-field.png]] | + | [[Image:Recommenders-completion-on-field.png]] |
== Completion on Anonymous Method Returns == | == Completion on Anonymous Method Returns == | ||
| − | [[Image:Recommenders-completion-on-method-return.png]] | + | [[Image:Recommenders-completion-on-method-return.png]] |
== Completion from Anonymous Inner Classes == | == Completion from Anonymous Inner Classes == | ||
| − | [[Image:Recommenders-completion-on-local-from-nested.png]] | + | [[Image:Recommenders-completion-on-local-from-nested.png]] |
== On-the-fly Code Analysis == | == On-the-fly Code Analysis == | ||
| − | Code Recommenders performs several static analyses on your code whenever you save your editor contents. However, sometimes you work a while with a dirty editor (i.e., editor contains un-safed changes). If code completion now was triggered on variables added after the last save code recommenders couldn't make any recommendations for these variables. This update now contains an on-the-fly analyzer that performs a flat analysis of your current method body whenever code completion is triggered on a previously unknown variable based on the information it obtains from the JDT AST. | + | Code Recommenders performs several static analyses on your code whenever you save your editor contents. However, sometimes you work a while with a dirty editor (i.e., editor contains un-safed changes). If code completion now was triggered on variables added after the last save code recommenders couldn't make any recommendations for these variables. This update now contains an on-the-fly analyzer that performs a flat analysis of your current method body whenever code completion is triggered on a previously unknown variable based on the information it obtains from the JDT AST. |
== Performance Improvements == | == Performance Improvements == | ||
| − | Code Completion's performance has been improve quite a lot. However, the loading of recommender models may take a second and thus may slow down your code completion on the first load. After the models are loaded, code completion usually takes between 10 to 50 ms.<br> | + | Code Completion's performance has been improve quite a lot. However, the loading of recommender models may take a second and thus may slow down your code completion on the first load. After the models are loaded, code completion usually takes between 10 to 50 ms.<br> |
| − | + | ||
| + | <br> | ||
= Overrides Completion = | = Overrides Completion = | ||
| − | + | [[Image:Recommenders-completion-on-class-body.png]]<br> | |
Revision as of 04:10, 15 February 2011
Contents
Calls Completion Engine
Completion on Declared Variables
Completion on Anonymous Method Returns
Completion from Anonymous Inner Classes
On-the-fly Code Analysis
Code Recommenders performs several static analyses on your code whenever you save your editor contents. However, sometimes you work a while with a dirty editor (i.e., editor contains un-safed changes). If code completion now was triggered on variables added after the last save code recommenders couldn't make any recommendations for these variables. This update now contains an on-the-fly analyzer that performs a flat analysis of your current method body whenever code completion is triggered on a previously unknown variable based on the information it obtains from the JDT AST.
Performance Improvements
Code Completion's performance has been improve quite a lot. However, the loading of recommender models may take a second and thus may slow down your code completion on the first load. After the models are loaded, code completion usually takes between 10 to 50 ms.
Overrides Completion
