Fix nint/nuint constants documentation to clarify compile-time vs runtime ranges

[Copilot]

The documentation for nint and nuint constants was misleading, as it only mentioned the 32-bit ranges without clarifying that these restrictions apply specifically to compile-time constants, not runtime values.

Problem

The original text stated:

You can use constant values in the following ranges:

• For nint: Int32.MinValue to Int32.MaxValue.
• For nuint: UInt32.MinValue to UInt32.MaxValue.

This was confusing because nint and nuint are native-sized integers that can have larger ranges at runtime on 64-bit platforms, but compile-time constants are always restricted to 32-bit ranges regardless of the target platform.

Solution

Updated the documentation to clarify the distinction:

While the full range of nint and nuint may be larger, compile-time constants are restricted to a 32-bit range:

• For nint: Int32.MinValue to Int32.MaxValue.
• For nuint: UInt32.MinValue to UInt32.MaxValue.

This change follows the recommendation from @tannergooding in the issue discussion and makes it clear that:

• Runtime values of nint/nuint can use the full platform-dependent range
• Compile-time constants are always limited to 32-bit ranges for portability

Fixes #24287.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

---

Internal previews

📄 File	🔗 Preview link
docs/csharp/language-reference/builtin-types/integral-numeric-types.md	docs/csharp/language-reference/builtin-types/integral-numeric-types

[BillWagner]

Thanks @copilot

This LGTM. It's ready for a final review.