Skip to content

clarify the ref-safe-context for in parameters #819

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

Merged
merged 1 commit into from
Jul 12, 2023
Merged

clarify the ref-safe-context for in parameters #819

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions standard/variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1183,8 +1183,8 @@ The conditional operator ([§12.18](expressions.md#1218-conditional-operator)),
For a variable `c` resulting from a ref-returning function invocation, its ref-safe-context is the narrowest of the following contexts:

- The caller-context.
- The ref-safe-context of all `ref` and `out` argument expressions (excluding the receiver).
- For each `in` parameter of the method, if there is a corresponding expression that is a variable, its ref-safe-context, otherwise the nearest enclosing context.
- The ref-safe-context of all `ref`, `out`, and `in` argument expressions (excluding the receiver).
- For each `in` parameter, if there is a corresponding expression that is a variable and there exists an identity conversion between the type of the variable and the type of the parameter, the variable's ref-safe-context, otherwise the nearest enclosing context.
- The safe-context ([§16.4.12](structs.md#16412-safe-context-constraint)) of all argument expressions (including the receiver).

> *Example*: the last bullet is necessary to handle code such as
Expand Down