https://github.com/aaronpuchert commented:
This is quite a lot of code to support something that is conceptually broken. You can't reference fields of a parent because it's only a parent in scoping/lookup. Nested type objects can very well exist without the parent. The only exception is when the nested type is not named and neither is the field. I don't think we should allow this. It is one of several cases where we've inadvertently not warned that users are referencing an entity that's actually not available in that context, and the proper fix is to reject such attributes. https://github.com/llvm/llvm-project/pull/233965 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
