You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[lldb] Refactor LookupInfo object to be per-language
Some months ago, the LookupInfo constructor logic was refactored to
not depend on language specific logic, and use languages plugins
instead. In this refactor, when the language type is unknown, a
single LookupInfo object will handle multiple languages. This doesn't
work well, as multiple languages might want to configure the LookupInfo
object in different ways. For example, different languages might want
to set the m_lookup_name differently from each other, but the previous
implementation would pick the first name a language provided, and
effectively ignored every other language. Other fields of the LookupInfo
object are also configured in incompatible ways.
This approach doesn't seem to be a problem upstream, since only
the C++/Objective-C language plugins are available, but it broke
downstream on the Swift fork, as adding Swift to the list of default
languages when the language type is unknown breaks C++ tests.
This patch makes it so instead of building a single LookupInfo
object for multiple languages, one LookupInfo object is built per
language instead.
rdar://159531216
0 commit comments