Skip to content

[intro.object] References are not potentially-overlapping subobjects #6160

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[intro.object] References are not potentially-overlapping subobjects #6160

wants to merge 1 commit into from

Conversation

frederick-vs-ja
Copy link
Contributor

Fixes #6158.

jensmaurer
jensmaurer requested changes Mar 5, 2023
View reviewed changes
@frederick-vs-ja frederick-vs-ja force-pushed the reference-is-not-subobject branch from 5e27ed4 to 83ee2ec Compare July 23, 2023 04:47
@tkoeppe tkoeppe requested a review from jensmaurer November 9, 2023 23:57
@frederick-vs-ja
Copy link
Contributor Author

@jensmaurer P2996 clarified that there're member subobjects corresponding to non-static reference data members. Is it intended that [[no_unique_address]] also affects these objects? If so, the current approach of this PR is incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jensmaurer jensmaurer Awaiting requested review from jensmaurer

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[intro.object] The term "potentially-overlapping subobject" doesn't seem to exclude reference members
2 participants
@frederick-vs-ja @jensmaurer