Community
Participate
Working Groups
Build 20021001 The search using hierarchy scopes could be optimized if the match locator new about this special scope. The hierarchy in the scope would never need to be computed. Instead the match locator would relsove all potential matches and exclude the one that are not a super or a sub type of of the focus type.
Time permitting for 2.1, if we see performance issues with hierarchies.
Changed SearchEngine and MatchLocator to know about HierarchyScope. When a Hierarchyscope is detected, its 'needsRefresh' flag is set to false, and MatchLocator forces a type resolve. It then excludes the matches not in the scope.
Does not work for binary types. Reopening.
Problem was that the binary type binding was cached even though there was a potential match in the attached source. Now get the binding after the resolution of all potential matches.
Verified.