-
Notifications
You must be signed in to change notification settings - Fork 1.6k
No, unique address! #1363
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
No, unique address! #1363
Conversation
MSVC is finally getting around to implementing `[[no_unique_address]]`, which will result in class layout differing with Clang. Let's comment out the uses that are not yet so commented until we reach compiler parity.
StephanTLavavej
left a comment
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. I checked out the branch and searched to verify that all occurrences of no_unique_address are commented out.
miscco
left a comment
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, am I understanding it correctly that the feature is WIP in the MSVC side and we do not want to interfere with their work?!
|
My understanding is to avoid ABI/ODR issues between TUs compiled with Clang and TUs compiled with MSVC, until both reach parity. |
|
Thanks for addressing this unique problem no-more. (There's no functional change here, so not Changelogging.) |
MSVC is finally getting around to implementing
[[no_unique_address]], which will result in class layout differing with Clang. Let's comment out the uses that are not yet so commented until we reach compiler parity.Related to MSVC-PR-280491, which implements
[[no_unique_address]]"for real" in MSVC.