[Lldb-commits] [lldb] [lldb][DWARFASTParserClang] Resolve nested types when parsing structures (PR #66879)

[Greg Clayton via lldb-commits]

https://github.com/clayborg requested changes to this pull request.

Is there a reason we need to complete nested types within a type? Seems like we can put that off until later. Right now if you parse a member function, any types it needs will be parsed lazily and only if needed, which is ok. If we start completing all types within types without ever needing to actually use then, it will make debugging slower and cause our memory usage to grow. I didn't see much explanation as to why this is needed in the bug report. 

https://github.com/llvm/llvm-project/pull/66879