proposals/csharp-11.0/numeric-intptr.md
[!INCLUDESpecletdisclaimer]
Champion issue: https://github.com/dotnet/csharplang/issues/6065
This is a revision on the initial native integers feature (spec), where the nint/nuint types were distinct from the underlying types System.IntPtr/System.UIntPtr.
In short, we now treat nint/nuint as simple types aliasing System.IntPtr/System.UIntPtr, like we do for int in relation to System.Int32. The System.Runtime.CompilerServices.RuntimeFeature.NumericIntPtr runtime feature flag triggers this new behavior.
C# provides a set of predefined struct types called the simple types. The simple types are identified through keywords, but these keywords are simply aliases for predefined struct types in the System namespace, as described in the table below.
| Keyword | Aliased type |
|---|---|
sbyte | System.SByte |
byte | System.Byte |
short | System.Int16 |
ushort | System.UInt16 |
int | System.Int32 |
uint | System.UInt32 |
nint | System.IntPtr |
nuint | System.UIntPtr |
long | System.Int64 |
ulong | System.UInt64 |
char | System.Char |
float | System.Single |
double | System.Double |
bool | System.Boolean |
decimal | System.Decimal |
[...]
C# supports eleven integral types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, and char. [...]
In other words, an unmanaged_type is one of the following:
sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, or bool.The implicit numeric conversions are:
sbyte to short, int, nint, long, float, double, or decimal.byte to short, ushort, int, uint, nint, nuint, long, ulong, float, double, or decimal.short to int, nint, long, float, double, or decimal.ushort to int, uint, nint, nuint, long, ulong, float, double, or decimal.int to nint, long, float, double, or decimal.uint to nuint, long, ulong, float, double, or decimal.nint to long, float, double, or decimal.nuint to ulong, float, double, or decimal.long to float, double, or decimal.ulong to float, double, or decimal.char to ushort, int, uint, nint, nuint, long, ulong, float, double, or decimal.float to double.[...]
An implicit constant expression conversion permits the following conversions:
int can be converted to type sbyte, byte, short, ushort, uint, nint, nuint, or ulong, provided the value of the constant_expression is within the range of the destination type.
[...]The explicit numeric conversions are the conversions from a numeric_type to another numeric_type for which an implicit numeric conversion does not already exist:
sbyte to byte, ushort, uint, nuint, ulong, or char.byte to sbyte or char.short to sbyte, byte, ushort, uint, nuint, ulong, or char.ushort to sbyte, byte, short, or char.int to sbyte, byte, short, ushort, uint, nuint, ulong, or char.uint to sbyte, byte, short, ushort, int, nint, or char.long to sbyte, byte, short, ushort, int, uint, nint, nuint, ulong, or char.nint to sbyte, byte, short, ushort, int, uint, nuint, ulong, or char.nuint to sbyte, byte, short, ushort, int, uint, nint, long, or char.ulong to sbyte, byte, short, ushort, int, uint, nint, nuint, long, or char.char to sbyte, byte, or short.float to sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, or decimal.double to sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, or decimal.decimal to sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, or double.[...]
The explicit enumeration conversions are:
sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, or decimal to any enum_type.sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, or decimal.Given two types T₁ and T₂, T₁ is a better conversion target than T₂ if one of the following holds:
T₁ to T₂ exists and no implicit conversion from T₂ to T₁ existsT₁ is Task<S₁>, T₂ is Task<S₂>, and S₁ is a better conversion target than S₂T₁ is S₁ or S₁? where S₁ is a signed integral type, and T₂ is S₂ or S₂? where S₂ is an unsigned integral type. Specifically: [...][...] The number of expressions in the argument_list shall be the same as the rank of the array_type, and each expression shall be of type int, uint, nint, nuint, long, or ulong, or shall be implicitly convertible to one or more of these types.
[...] The number of expressions in the argument_list shall be the same as the rank of the array_type, and each expression shall be of type int, uint, nint, nuint, long, or ulong, or shall be implicitly convertible to one or more of these types.
[...] The run-time processing of an array access of the form P[A], where P is a primary_no_array_creation_expression of an array_type and A is an argument_list, consists of the following steps:
[...]
int, uint, nint, nuint, long, ulong. The first type in this list for which an implicit conversion exists is chosen. [...]Unary operator overload resolution is applied to select a specific operator implementation. Predefined ++ and -- operators exist for the following types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, and any enum type.
The predefined unary plus operators are:
...
nint operator +(nint x);
nuint operator +(nuint x);
The predefined unary minus operators are:
Integer negation:
...
nint operator –(nint x);
Predefined ++ and -- operators exist for the following types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, and any enum type.
In addition, a default_value_expression is a constant expression if the type is one of the following value types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, bool, or any enumeration type.
The predefined bitwise complement operators are:
...
nint operator ~(nint x);
nuint operator ~(nuint x);
Predefined ++ and -- operators exist for the following types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, and any enum type.
The predefined multiplication operators are listed below. The operators all compute the product of x and y.
Integer multiplication:
...
nint operator *(nint x, nint y);
nuint operator *(nuint x, nuint y);
The predefined division operators are listed below. The operators all compute the quotient of x and y.
Integer division:
...
nint operator /(nint x, nint y);
nuint operator /(nuint x, nuint y);
The predefined remainder operators are listed below. The operators all compute the remainder of the division between x and y.
Integer remainder:
...
nint operator %(nint x, nint y);
nuint operator %(nuint x, nuint y);
Integer addition:
...
nint operator +(nint x, nint y);
nuint operator +(nuint x, nuint y);
Integer subtraction:
...
nint operator –(nint x, nint y);
nuint operator –(nuint x, nuint y);
The predefined shift operators are listed below.
Shift left:
...
nint operator <<(nint x, int count);
nuint operator <<(nuint x, int count);
Shift right:
...
nint operator >>(nint x, int count);
nuint operator >>(nuint x, int count);
The >> operator shifts x right by a number of bits computed as described below.
When x is of type int, nint or long, the low-order bits of x are discarded, the remaining bits are shifted right, and the high-order empty bit positions are set to zero if x is non-negative and set to one if x is negative.
When x is of type uint, nuint or ulong, the low-order bits of x are discarded, the remaining bits are shifted right, and the high-order empty bit positions are set to zero.
Unsigned shift right:
...
nint operator >>>(nint x, int count);
nuint operator >>>(nuint x, int count);
For the predefined operators, the number of bits to shift is computed as follows: [...]
x is nint or nuint, the shift count is given by the low-order five bits of count on a 32 bit platform, or the lower-order six bits of count on a 64 bit platform.The predefined integer comparison operators are:
...
bool operator ==(nint x, nint y);
bool operator ==(nuint x, nuint y);
bool operator !=(nint x, nint y);
bool operator !=(nuint x, nuint y);
bool operator <(nint x, nint y);
bool operator <(nuint x, nuint y);
bool operator >(nint x, nint y);
bool operator >(nuint x, nuint y);
bool operator <=(nint x, nint y);
bool operator <=(nuint x, nuint y);
bool operator >=(nint x, nint y);
bool operator >=(nuint x, nuint y);
The predefined integer logical operators are:
...
nint operator &(nint x, nint y);
nuint operator &(nuint x, nuint y);
nint operator |(nint x, nint y);
nuint operator |(nuint x, nuint y);
nint operator ^(nint x, nint y);
nuint operator ^(nuint x, nuint y);
A constant expression may be either a value type or a reference type. If a constant expression is a value type, it must be one of the following types: sbyte, byte, short, ushort, int, uint, nint, nuint, long, ulong, char, float, double, decimal, bool, or any enumeration type.
[...]
An implicit constant expression conversion permits a constant expression of type int to be converted to sbyte, byte, short, ushort, uint, nint, nuint, or ulong, provided the value of the constant expression is within the range of the destination type.
Array elements are accessed using element_access expressions of the form A[I₁, I₂, ..., Iₓ], where A is an expression of an array type and each Iₑ is an expression of type int, uint, nint, nuint, long, ulong, or can be implicitly converted to one or more of these types. The result of an array element access is a variable, namely the array element selected by the indices.
[...]
Additionally, in an unsafe context, the set of available explicit conversions is extended to include the following explicit pointer conversions:
sbyte, byte, short, ushort, int, uint, nint, nuint, long, or ulong to any pointer_type.sbyte, byte, short, ushort, int, uint, nint, nuint, long, or ulong.[...]
In a pointer element access of the form P[E], P shall be an expression of a pointer type other than void*, and E shall be an expression that can be implicitly converted to int, uint, nint, nuint, long, or ulong.
In an unsafe context, the + operator and – operator can be applied to values of all pointer types except void*. Thus, for every pointer type T*, the following operators are implicitly defined:
[...]
T* operator +(T* x, nint y);
T* operator +(T* x, nuint y);
T* operator +(nint x, T* y);
T* operator +(nuint x, T* y);
T* operator -(T* x, nint y);
T* operator -(T* x, nuint y);
Given an expression P of a pointer type T* and an expression N of type int, uint, nint, nuint, long, or ulong, the expressions P + N and N + P compute the pointer value of type T* that results from adding N * sizeof(T) to the address given by P. Likewise, the expression P – N computes the pointer value of type T* that results from subtracting N * sizeof(T) from the address given by P.
One of the main impacts of this design is that System.IntPtr and System.UIntPtr gain some built-in operators (conversions, unary and binary).
Those include checked operators, which means that the following operators on those types will now throw when overflowing:
IntPtr + intIntPtr - intIntPtr -> intlong -> IntPtrvoid* -> IntPtrThis design means that nint and nuint can simply be emitted as System.IntPtr and System.UIntPtr, without the use of System.Runtime.CompilerServices.NativeIntegerAttribute.
Similarly, when loading metadata NativeIntegerAttribute can be ignored.