[cfe-dev] ElaboratedType, QualifiedNameType and TypenameType.

Douglas Gregor dgregor at apple.com
Mon Mar 29 11:43:32 PDT 2010


On Mar 22, 2010, at 5:13 PM, Douglas Gregor wrote:
> 
> 
> ... and after talking with John for a bit, we're starting to like the following scheme:
> 
> DependentQualifiedNameType: captures all qualified types with dependent names, including elaborated-type-specifiers (class/struct/union/enum), typename-specifiers (typename), and implied dependent name types (X<T>::type as a base class).
> 
> ElaboratedType: captures all elaborated-type-specifiers (class/struct/union/enum), typename-specifiers (typename), and qualified names (no other adornment) where we were able to look up the type. These nodes can have an optional NestedNameSpecifier, and will always have either a class/struct/union/enum keyword or a nested-name-specifier.

Enea or Abramo, are either of you working on this? If not, I'll go ahead and implement this change.

	- Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20100329/2b0b53c3/attachment.html>


More information about the cfe-dev mailing list