[Lldb-commits] [lldb] [lldb][DWARFASTParserClang] Adjust language type for conflicting Objective-C++ forward declarations (PR #130768)

[Pavel Labath via lldb-commits]

labath wrote:

oh boy.. this is going to be messy.

So what would happen if we treated `class NSString` and `@class NSString` as two distinct types? I guess that would be a problem because then we could end up with duplicate versions of everything that depends on that type (two `void foo(NSString)`s, depending on whether it's parsed in a C++ or ObjC CU)? (I'm guessing the reason that it uses this hack is because it wants to refer to NSString from generic code.)

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