-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Automatically port ReadOnlySpan.GetPinnableReference #3179
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
Conversation
rpetrusha
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.
I've suggested some changes, @carlossanlop.
| <Docs> | ||
| <summary>To be added.</summary> | ||
| <returns>To be added.</returns> | ||
| <summary>A read-only reference to an object of type T that can be used for pinning, and is required to support the use of span within a fixed statement.</summary> |
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.
| <summary>A read-only reference to an object of type T that can be used for pinning, and is required to support the use of span within a fixed statement.</summary> | |
| <summary>A read-only reference to an object of type <typeparamref>T</typeparamref> that can be used for pinning. It is required to support the use of a span within a <code>fixed</code> statement.</summary> |
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.
@rpetrusha shouldn't we be using <typeparamref name="T" /> instead? Or are both valid? I ask because this is the first time I see this format.
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.
Sorry, @carlossanlop. Yes, we should be using <typeparmref name="T" />. I'm not sure what I was thinking.
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.
no worries!
Co-Authored-By: Ron Petrusha <[email protected]>
|
Thanks for the additional changes, @carlossanlop. I'll merge your PR now. |
Summary and return.