[Idea] Reference to enclosing type by `Parent`, akin to `Self` but "one level up"

[Pippin (Ethan Pippin)]

@Sajjon

This may look like a small thing... but this would allow us to write more powerful Xcode Templates and I believe it will be helpful for macro authors as well.

For macros, this would be solved with the following feature instead,

[Macros] Accessing the "parent context" of a syntax node passed to a macro

Hi all, The expansion operation of a macro implementation only receives source code corresponding to how a macro is spelled (e.g., #stringify(x + y) or @AddCompletionHandler) and any syntax it directly operates on (e.g., the declaration node to which @AddCompletionHandler was attached). These macros are not provided with any "context" information, e.g., is the attached node a member of a struct? Is the expansion inside a function? I suggest that we introduce an API on MacroExpansionContext tha…

Additionally, this adds a special rule for "types" and adds a new keyword - that's only confusing. How would this also work with types actually called Parent, or any other proposed keyword?

• Code search results · GitHub