Bug 427305 - [Xbase] Optimize Feature Scope
Summary: [Xbase] Optimize Feature Scope
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.5.0   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-03 12:39 EST by Sven Efftinge CLA
Modified: 2015-02-09 08:56 EST (History)
1 user (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 Sven Efftinge CLA 2014-02-03 12:39:54 EST 
Featurecalls are currently eagerly resolving all candidates.
We should improve this behavior by exiting the resolution when definitive candidates, such as local variables have been found.
Comment 1 Sebastian Zarnekow CLA 2014-02-03 12:42:34 EST 
See ImportedNamesTest for the first test case which imports names like java.lang.s
Comment 2 Sebastian Zarnekow CLA 2014-02-04 03:37:17 EST 
For the record, local vars are already using LocalVariableScope.looksLikeLocalVariable() and friends. The same should be used for *visible* fields
Comment 3 Sebastian Zarnekow CLA 2014-02-04 07:05:52 EST 
One possible solution is to defer the lookup in the type scope and return a lazy description instead. It would only be evaluated if all other descriptions failed to link properly.
Comment 4 Sebastian Zarnekow CLA 2015-02-09 08:56:32 EST 
Unfortunately not 2.8