Skip to content

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

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jul 8, 2025
Merged

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

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
35fa7c9
Initial plan
Copilot Jul 7, 2025
783e0d4
Fix nint/nuint constants documentation to clarify compile-time vs run…
Copilot Jul 7, 2025
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 docs/csharp/language-reference/builtin-types/integral-numeric-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Native sized integer types have special behavior because the storage is determin

:::code language="csharp" source="snippets/shared/NativeIntegerTypes.cs" id="MinMax":::

- You can use constant values in the following ranges:
- While the full range of `nint` and `nuint` may be larger, compile-time constants are restricted to a 32-bit range:
- For `nint`: <xref:System.Int32.MinValue?displayProperty=nameWithType> to <xref:System.Int32.MaxValue?displayProperty=nameWithType>.
- For `nuint`: <xref:System.UInt32.MinValue?displayProperty=nameWithType> to <xref:System.UInt32.MaxValue?displayProperty=nameWithType>.
- The compiler provides implicit and explicit conversions to other numeric types. For more information, see [Built-in numeric conversions](numeric-conversions.md).
Expand Down
Loading