mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-23 00:45:28 +02:00
a7bfdd2802
When AST is used to resolve binding for class-name and elaborated-type-specifier is found matching [basic.lookup.elab] rule introducing the class-name, behavior of CPPSemantics.resolveAmbiguities() is different in presence of index. If there is no index, CPPVisitor.createBinding() for ICPPASTElaboratedTypeSpecifier creates binding for class-name as introducing the name. When later lookup finds this binding all is good because binding is declared before the use site. If index is available, lookup for class-name fails in AST too but now matching entry is found in the AST index. When later lookup finds this index binding CPPSemantics.declaredBefore() returns false because it does not look in AST index and only checks project index. To fix this additionally check if ICPPClassType object is in AST index, as we already do for ICPPConstructor. This way declaredBefore() does almost the same thing as isReachableFromAst() and lookup succeeds returning the same binding from index. |
||
|---|---|---|
| .. | ||
| org.eclipse.cdt.core | ||
| org.eclipse.cdt.core.linux | ||
| org.eclipse.cdt.core.linux.aarch64 | ||
| org.eclipse.cdt.core.linux.ppc64le | ||
| org.eclipse.cdt.core.linux.x86_64 | ||
| org.eclipse.cdt.core.macosx | ||
| org.eclipse.cdt.core.native | ||
| org.eclipse.cdt.core.tests | ||
| org.eclipse.cdt.core.win32 | ||
| org.eclipse.cdt.core.win32.x86_64 | ||
| org.eclipse.cdt.ui | ||
| org.eclipse.cdt.ui.tests | ||
| pom.xml | ||