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

Backport API docs for System.Buffers #51296

Closed
wants to merge 3 commits into from
Closed

Backport API docs for System.Buffers #51296

wants to merge 3 commits into from

Conversation

jeffhandley
Copy link
Member

Fixes #48967, backporting the API docs for System.Buffers. This port utilizes changes to the DocsPortingTool from a couple of open PRs so that generic APIs are handled properly.

@jeffhandley jeffhandley added documentation Documentation bug or enhancement, does not impact product or test code area-System.Buffers labels Apr 15, 2021
@ghost
Copy link

ghost commented Apr 15, 2021

Tagging subscribers to this area: @tannergooding, @pgovind, @GrabYourPitchforks
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #48967, backporting the API docs for System.Buffers. This port utilizes changes to the DocsPortingTool from a couple of open PRs so that generic APIs are handled properly.

Author: jeffhandley
Assignees: -
Labels:

area-System.Buffers, documentation

Milestone: -

/// <summary>
/// Owner of Memory<typeparamref name="T"/> that is responsible for disposing the underlying memory appropriately.
/// </summary>
#pragma warning disable CS1574 // XML comment has cref attribute that could not be resolved (System.Buffers.MemoryPool{T}.Rent)
Copy link
Member Author

Choose a reason for hiding this comment

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

This was a little interesting. System.Buffers.MemoryPool<T> isn't visible within the System.Buffers build because of it coming from System.Private.CoreLib. Retaining the <see cref> reference to it seemed valuable though. If we see enough of these situations, it would be possible for the DocsPortingTool to detect this situation and apply the #pragma automatically.

@jeffhandley
Copy link
Member Author

@carlossanlop I'm not sure that enabling doc generation is working as expected for this library. This project is odd in that all of the types are defined in files included in System.Private.CoreLib\src\System.Private.CoreLib.Shared.projitems and built as part of System.Private.CoreLib.

@jeffhandley
Copy link
Member Author

I'm going to close this PR for now. I'll revisit this port after we've gotten some other libraries ported that don't have the same complications as Buffers.

@jeffhandley jeffhandley closed this May 5, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jun 19, 2021
@jeffhandley jeffhandley deleted the jeffhandley/backport-docs-buffers branch August 1, 2021 20:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Buffers documentation Documentation bug or enhancement, does not impact product or test code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

System.Buffers: Backport MS Docs documentation to triple slash
2 participants