Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359377

Summary:	[Xbase] optimize computation of CompletionProposals FeatureCall_declaredType
Product:	[Modeling] TMF	Reporter:	Holger Schill <Holger.Schill>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	sebastian.zarnekow, sven.efftinge
Version:	2.1.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	359367
Bug Blocks:

Description Holger Schill

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

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

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 ***