-
Notifications
You must be signed in to change notification settings - Fork 341
[lldb] Wire up reflection support for Builtin.FixedArray #9928
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
[lldb] Wire up reflection support for Builtin.FixedArray #9928
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me with 1 fix.
At some point it would be nice to split these functions into smaller functions that deal with the different type info types. GetChildCompilerTypeAtIndex
will be almost 400 lines long with this change.
return llvm::createStringError("Expected fixed array, but found: " + | ||
type.GetMangledTypeName().GetString()); | ||
return ts->RemangleAsType(dem, dem_array_type->getChild(1), | ||
ts->GetManglingFlavor()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
auto flavor = SwiftLanguageRuntime::GetManglingFlavor(
type.GetMangledTypeName().GetStringRef());
return ts->RemangleAsType(dem, dem_array_type->getChild(1), flavor);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point it would be nice to split these functions into smaller functions that deal with the different type info types. GetChildCompilerTypeAtIndex will be almost 400 lines long with this change.
I think the way to go is to factor out common code between GetChildCompilerTypeAtIndex, GetNumChildren, and GetChildMembeWithName.
No test in the testsuite triggeres this code path, except for the new ValueGeneric tes, which triggers it for entirely the wrong reason. I added a new test that exercises the case that is mentioned in the comment to make sure that this is indeed obsolete.
@swift-ci test |
8857333
to
2472c96
Compare
@swift-ci test |
@swift-ci test windows |
@swift-ci test macos |
test with swiftlang/swift#79088 |
No description provided.