Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/System/Double.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2947,7 +2947,7 @@ This method correctly handles floating-point values and so `2.0` and `3.0` will
</Parameters>
<Docs>
<param name="d">A double-precision floating-point number.</param>
<summary>Determines whether the specified value is normal.</summary>
<summary>Determines whether the specified value is not NaN, not infinite, not subnormal, and not zero.</summary>
Copy link
Member

Choose a reason for hiding this comment

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

If you're wanting to not be repetitive, then repeating subnormal doesn't really help either.. The technical definition is:

Suggested change
<summary>Determines whether the specified value is not NaN, not infinite, not subnormal, and not zero.</summary>
<summary>Determines whether the specified value is a finite non-zero value with magnitude greater than or equal to <c>2<sup>-1022</sup></c>.</summary>

Copy link
Member

@tannergooding tannergooding Feb 4, 2026

Choose a reason for hiding this comment

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

I would expect Single, Half, NFloat, and INumberBase<TSelf> to all be updated in the same PR.

I would also expect other definitions like IsInfinite, IsSubnormal, IsFinite, etc to be updated if required.

Copy link
Member

Choose a reason for hiding this comment

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

And as per the Copilot guidance below, the summary and remarks are effectively just mirroring eachother now, so the remarks need to either be removed or updated.

<returns>
<see langword="true" /> if the value is normal; <see langword="false" /> otherwise.</returns>
<remarks>This effectively checks the value is not NaN, not infinite, not subnormal, and not zero.</remarks>
Comment on lines 2952 to 2953
Copy link

Copilot AI Feb 4, 2026

Choose a reason for hiding this comment

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

The updated

explains what “normal” means, but the text still relies on the term “normal” without the definition. Consider updating to use the same explicit criteria (or add the definition there) so readers don’t have to infer it from the summary/remarks.

Also, the criteria list is now repeated in both

and , which creates duplication that can drift over time. Consider removing the redundant list from or using for additional context instead of repeating the same definition.

Suggested change
<see langword="true" /> if the value is normal; <see langword="false" /> otherwise.</returns>
<remarks>This effectively checks the value is not NaN, not infinite, not subnormal, and not zero.</remarks>
<see langword="true" /> if the value is not NaN, not infinite, not subnormal, and not zero; <see langword="false" /> otherwise.</returns>
<remarks>Use this method to determine whether a double-precision floating-point number is a normal value before performing calculations that assume finite, nonzero magnitudes.</remarks>

Copilot uses AI. Check for mistakes.
Expand Down
Loading