Skip to content
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

Treat field access into a class value expression as a value expression. #3357

Merged

Conversation

zygoloid
Copy link
Contributor

@zygoloid zygoloid commented Nov 1, 2023

Per the design, field access into a class value expression is a value expression, even though we could produce an ephemeral reference expression instead and avoid performing a value binding. This slightly pessimizes class member access in some cases, but we should be able to restore the old generated code by deferring actually performing the value binding until a value expression is needed.

Per the design, field access into a class value expression is a value
expression, even though we could produce an ephemeral reference
expression instead and avoid performing a value binding. This slightly
pessimizes class member access in some cases, but we should be able to
restore the old code by deferring actually performing the value binding
until a value expression is needed.
@github-actions github-actions bot requested a review from jonmeow November 1, 2023 21:37
@jonmeow jonmeow added this pull request to the merge queue Nov 2, 2023
Merged via the queue into carbon-language:trunk with commit 35c2142 Nov 2, 2023
8 checks passed
@zygoloid zygoloid deleted the toolchain-class-memaccess-category branch November 10, 2023 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants