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

Ensure XML doc comments exist for the nested classes and IsSupported properties for intrinsics #106091

Merged
merged 3 commits into from
Aug 19, 2024

Conversation

tannergooding
Copy link
Member

This resolves #83165

@tannergooding
Copy link
Member Author

CC. @carlossanlop

@carlossanlop
Copy link
Member

Thanks @tannergooding ! So it turns out we were just missing the actual xml docs in triple slash. I thought the reported bug was something in the way the xmls were getting generated, or the porting tool not being capable of finding nested types.

@gewarren could you help with a language review?

Copy link
Contributor

@gewarren gewarren left a comment

Choose a reason for hiding this comment

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

I left a few suggestions that looks like they could be applied throughout if you like them.

@tannergooding
Copy link
Member Author

Updated to include the feedback

@tannergooding
Copy link
Member Author

tannergooding commented Aug 12, 2024

CC. @carlossanlop, @gewarren could this get sign-off so it can be merged?

@tannergooding
Copy link
Member Author

Ping. @carlossanlop, @gewarren could this get sign-off so it can be merged?

/// </summary>
[CLSCompliant(false)]
public abstract class Aes : ArmBase
{
internal Aes() { }

/// <summary>Gets a value that indicates whether the APIs in this class are supported.</summary>
Copy link
Member

Choose a reason for hiding this comment

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

I think this should instead say something along the lines of "Always returns false, indicating that the APIs in this class are not supported."

Copy link
Member

Choose a reason for hiding this comment

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

Same suggestion for all the similar *.NotSupported.cs IsSupported properties that return false.

Copy link
Member Author

Choose a reason for hiding this comment

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

We have 1 set of docs that exist, not separate ones for *.cs for *.PlatformNotSupported.cs

The *.PlatformNotSupported.cs are purely implementation details for corelib to be more optimal

Copy link
Contributor

@gewarren gewarren left a comment

Choose a reason for hiding this comment

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

LGTM except for a handful of missing periods in the summary. You could find/replace intrinsics</summary> and also when the closing summary tag is on the following line.

@tannergooding
Copy link
Member Author

@carlossanlop, do these need to be backported to resolve the 9.0 issue?

@github-actions github-actions bot locked and limited conversation to collaborators Sep 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nested classes in System.Runtime.Intrinsics are missing xml doc comments
3 participants