Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359377 - [Xbase] optimize computation of CompletionProposals FeatureCall_declaredType
Summary: [Xbase] optimize computation of CompletionProposals FeatureCall_declaredType
Status: CLOSED DUPLICATE of bug 416144
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 359367
Blocks:
  Show dependency tree
 
Reported: 2011-09-29 05:23 EDT by Holger Schill CLA
Modified: 2013-09-16 12:50 EDT (History)
2 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 Holger Schill CLA 2011-09-29 05:23:06 EDT 
In XbaseProposalProvider.completeXFeatureCall_DeclaringType and AbstractXbaseWithAnnotationsProposalProvider.completeXAnnotationValueFieldReference_DeclaringType need to optimize the filter for completeJavaTypes. Now it can take up to 5 seconds (on my machine). 

To reproduce this add a Annotation to a XtendClass and invoke the contentAssist inside the brackets of the annotation.
Comment 1 Sebastian Zarnekow CLA 2011-10-17 16:33:05 EDT 
Non static features and operations should be marked as invalid in the context of an annotation. The default proposal list does not make any sense to me :-)
Comment 2 Sven Efftinge CLA 2013-09-16 12:50:38 EDT 
comment #0 is a duplicate of bug #416144
comment #1 is outdated.

*** This bug has been marked as a duplicate of bug 416144 ***