Skip to content

[lldb] Factor out iteration over runtime types from GetChildCompilerT… #10533

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

Open
wants to merge 1 commit into
base: swift/release/6.2
Choose a base branch
from

Conversation

adrian-prantl
Copy link

…ypeAtIndex()

This patch introduces a new class SwiftRuntimeTypeVisitor that exists to unify iteration over runtime type information. The visitor callback has closure parameters that can be called to make additional expensive queries on a child.

TODO: This is not the final evolution step.

  • We probably should remove the "depth" parameter entirely and implement the access path computation for GetIndexOfChildMemberWithName at a different layer.

  • We could cache the results for the last execution context.

@adrian-prantl adrian-prantl requested a review from a team as a code owner April 23, 2025 21:08
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test macOS

@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test

1 similar comment
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl adrian-prantl force-pushed the runtime-type-visitor branch 2 times, most recently from e048cc4 to 744d7b5 Compare April 24, 2025 22:49
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test

…ypeAtIndex()

This patch introduces a new class SwiftRuntimeTypeVisitor that exists
to unify iteration over runtime type information. The visitor callback
has closure parameters that can be called to make additional expensive
queries on a child.

TODO: This is not the final evolution step.

- We probably should remove the "depth" parameter entirely and implement the access path computation for GetIndexOfChildMemberWithName at a different layer.

- We could cache the results for the last execution context.
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test macOS

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.

2 participants