Skip to content

[CIR] Treat cir.record class and struct types equivalently. #1564

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

Merged
merged 2 commits into from
Apr 16, 2025

Conversation

andykaylor
Copy link
Collaborator

When we create a cir.record type, we track the RecordKind according to whether the source code declared the type using struct or class even though these are semantically equivalent. The distinction is used in naming the type when we lower to the LLVM dialect.

This change updates the code to remove the last place where we were handling class and struct records differently.

When we create a `cir.record` type, we track the `RecordKind` according to
whether the source code declared the type using `struct` or `class` even
though these are semantically equivalent. The distinction is used in naming
the type when we lower to the LLVM dialect.

This change updates the code to remove the last place where we were handling
class and struct records differently.
Copy link
Member

@bcardosolopes bcardosolopes left a comment

Choose a reason for hiding this comment

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

LGTM pending removing outdated comment on verifier.

@bcardosolopes bcardosolopes merged commit 204c03e into llvm:main Apr 16, 2025
9 checks passed
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