Skip to content

🍒 [LLDB] Refactor demangler range tracking #10767

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

charles-zablit
Copy link

charles-zablit and others added 2 commits May 30, 2025 14:53
This PR is a subset of the commits made in
#10710.

The most notable change is the addition of `PrefixRange` and
`SuffixRange` which are a catch-all to track anything after or before a
function's demangled name. In the case of Swift, this allows to add
support for name highlighting without having to track the range of the
scope and specifiers of a function (this will come in another PR).
…rning (llvm#141790)

llvm#140762 introduces some
compilation warnings in `lldb/unittests/Core/MangledTest.cpp`. This
patch adds explicit default initialization to `DemangledNameInfo` to
suppress those warnings.

We only had the default initialization values to `PrefixRange` and
`SuffixRange` because they are the only _optional_ fields of the
structure.
@Michael137
Copy link

@swift-ci test

@adrian-prantl adrian-prantl merged commit 88f358a into swift/release/6.2 Jun 3, 2025
3 checks passed
@adrian-prantl adrian-prantl deleted the charles-zablit/lldb/refactor-demangler-range-tracking-to-6.2 branch June 3, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants