Skip to content

Conversation

@carlossanlop
Copy link
Contributor

Summary and return.

@carlossanlop carlossanlop added new-content Indicates PRs that contain new articles waiting-on-reviews Indicates PRs that cannot be merged because of the lack of reviews 🏁 Release: .NET Core 2.x Identifies work items for the .NET Core 2.x releases labels Sep 14, 2019
@carlossanlop carlossanlop added this to the September 2019 milestone Sep 14, 2019
@carlossanlop carlossanlop self-assigned this Sep 14, 2019
Copy link

@rpetrusha rpetrusha left a 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>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<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>

Copy link
Contributor Author

@carlossanlop carlossanlop Sep 18, 2019

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.

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.

Copy link
Contributor Author

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]>
@rpetrusha
Copy link

Thanks for the additional changes, @carlossanlop. I'll merge your PR now.

@rpetrusha rpetrusha merged commit deff009 into dotnet:master Sep 26, 2019
@carlossanlop carlossanlop deleted the GetPinnableReference2X branch September 26, 2019 16:26
@mairaw mairaw removed the waiting-on-reviews Indicates PRs that cannot be merged because of the lack of reviews label Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🏁 Release: .NET Core 2.x Identifies work items for the .NET Core 2.x releases new-content Indicates PRs that contain new articles

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants