Skip to content

Code-fence C# conversion keywords in numeric conversions doc #54760

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
BillWagner merged 3 commits into from
Jul 15, 2026
+11 −11
Merged

Code-fence C# conversion keywords in numeric conversions doc #54760

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2acd682
Initial plan
Copilot Jul 14, 2026
5ab0eb4
Fix overlocalization risk by codefencing C# conversion keywords
Copilot Jul 14, 2026
b6a7bce
Address review: code-fence implicit-table type keywords
Copilot Jul 14, 2026
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
22 changes: 11 additions & 11 deletions docs/csharp/language-reference/builtin-types/numeric-conversions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,17 +22,17 @@ The following table shows the predefined implicit conversions between the built-

| From | To |
|------------------------------------------|--------|
| [sbyte](integral-numeric-types.md) | `short`, `int`, `long`, `float`, `double`, `decimal`, or `nint` |
| [byte](integral-numeric-types.md) | `short`, `ushort`, `int`, `uint`, `long`, `ulong`, `float`, `double`, `decimal`, `nint`, or `nuint` |
| [short](integral-numeric-types.md) | `int`, `long`, `float`, `double`, `decimal`, or `nint` |
| [ushort](integral-numeric-types.md) | `int`, `uint`, `long`, `ulong`, `float`, `double`, `decimal`, `nint`, or `nuint` |
| [int](integral-numeric-types.md) | `long`, `float`, `double`, `decimal`, or `nint` |
| [uint](integral-numeric-types.md) | `long`, `ulong`, `float`, `double`, `decimal`, or `nuint` |
| [long](integral-numeric-types.md) | `float`, `double`, or `decimal` |
| [ulong](integral-numeric-types.md) | `float`, `double`, or `decimal` |
| [float](floating-point-numeric-types.md) | `double` |
| [nint](integral-numeric-types.md) | `long`, `float`, `double`, or `decimal` |
| [nuint](integral-numeric-types.md) | `ulong`, `float`, `double`, or `decimal` |
| [`sbyte`](integral-numeric-types.md) | `short`, `int`, `long`, `float`, `double`, `decimal`, or `nint` |
Comment thread
BillWagner marked this conversation as resolved.
| [`byte`](integral-numeric-types.md) | `short`, `ushort`, `int`, `uint`, `long`, `ulong`, `float`, `double`, `decimal`, `nint`, or `nuint` |
| [`short`](integral-numeric-types.md) | `int`, `long`, `float`, `double`, `decimal`, or `nint` |
| [`ushort`](integral-numeric-types.md) | `int`, `uint`, `long`, `ulong`, `float`, `double`, `decimal`, `nint`, or `nuint` |
| [`int`](integral-numeric-types.md) | `long`, `float`, `double`, `decimal`, or `nint` |
| [`uint`](integral-numeric-types.md) | `long`, `ulong`, `float`, `double`, `decimal`, or `nuint` |
| [`long`](integral-numeric-types.md) | `float`, `double`, or `decimal` |
| [`ulong`](integral-numeric-types.md) | `float`, `double`, or `decimal` |
| [`float`](floating-point-numeric-types.md) | `double` |
| [`nint`](integral-numeric-types.md) | `long`, `float`, `double`, or `decimal` |
| [`nuint`](integral-numeric-types.md) | `ulong`, `float`, `double`, or `decimal` |

> [!NOTE]
> The implicit conversions from `int`, `uint`, `long`, `ulong`, `nint`, or `nuint` to `float` and from `long`, `ulong`, `nint`, or `nuint` to `double` can cause a loss of precision, but never a loss of an order of magnitude. The other implicit numeric conversions never lose any information.
Expand Down
Loading