mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-23 14:42:11 +02:00
![]() When the variable template was instantiated through an implicit name (constructor), the current look-up point was used to determine whether or not the variable instance was an explicit specialization but it's not enough. During resolution of implicit name, the look-up was on the constructor call, not on the variable instance. I'm not sure if the current look-up should be changed but we already had the information about the AST node being an explicit specialization down the stack, so we just pass that info now and it seems safer than changing the look-up point. |
||
---|---|---|
.. | ||
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 |