Skip to content

[lldb] Implement TypeSystemSwiftTypeRef::ShouldPrintAsOneLiner #2231

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

kastiglione
Copy link

Implement TypeSystemSwiftTypeRef::ShouldPrintAsOneLiner to match the SwiftASTContext implementation.

rdar://68171384

return eLazyBoolCalculate;
};
VALIDATE_AND_RETURN(impl, ShouldPrintAsOneLiner, type,
(ReconstructType(type), valobj));

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks sufficiently generic that you could hoist it all the way into the TypeSystemSwift base class and delete the SwiftASTContext implementation.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's nothing TypeSystemSwiftTypeRef-specific.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That said, I'm also fine with landing it as is and doing that as an NFC refactor later.

return eLazyBoolCalculate;
};
VALIDATE_AND_RETURN(impl, ShouldPrintAsOneLiner, type,
(ReconstructType(type), valobj));

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That said, I'm also fine with landing it as is and doing that as an NFC refactor later.

@kastiglione
Copy link
Author

@swift-ci test

@kastiglione
Copy link
Author

I'll do an NFC refactor later. There may be a few functions like this.

@kastiglione kastiglione merged commit a01bdfb into swift/main Dec 14, 2020
@kastiglione kastiglione deleted the lldb-Implement-TypeSystemSwiftTypeRef-ShouldPrintAsOneLiner branch December 14, 2020 18:13
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