clarify the ref-safe-context for in parameters
#819
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jskeet
approved these changes
Jun 26, 2023
BillWagner
added
the
meeting: discuss
gafter
approved these changes
Jul 12, 2023
The ref safe context for an `in` parameter is different when the `in` argument is passed by reference vs. when a copy is made. Fixes dotnet#296
BillWagner
force-pushed
the
in-ref-safety
branch
from
7f9e34a to
fd66ac5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ref safe context for an
inparameter is different when theinargument is passed by reference vs. when a copy is made.Fixes #296