Skip to content

Commit

Permalink
Misplaced question mark for nullable value type conversion (dotnet#1176)
Browse files Browse the repository at this point in the history
  • Loading branch information
jcouv authored Sep 17, 2024
1 parent 9f8d893 commit 149297d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion standard/conversions.md
Original file line number Diff line number Diff line change
Expand Up @@ -770,7 +770,7 @@ A user-defined explicit conversion from a type `S` to a type `T` exists if a u
***Nullable conversions*** permit predefined conversions that operate on non-nullable value types to also be used with nullable forms of those types. For each of the predefined implicit or explicit conversions that convert from a non-nullable value type `S` to a non-nullable value type `T` ([§10.2.2](conversions.md#1022-identity-conversion), [§10.2.3](conversions.md#1023-implicit-numeric-conversions), [§10.2.4](conversions.md#1024-implicit-enumeration-conversions), [§10.2.11](conversions.md#10211-implicit-constant-expression-conversions), [§10.3.2](conversions.md#1032-explicit-numeric-conversions) and10.3.3](conversions.md#1033-explicit-enumeration-conversions)), the following nullable conversions exist:
- An implicit or explicit conversion from `S?` to `T?`
- An implicit or explicit conversion from `S` to `T`?
- An implicit or explicit conversion from `S` to `T?`
- An explicit conversion from `S?` to `T`.
A nullable conversion is itself classified as an implicit or explicit conversion.
Expand Down

0 comments on commit 149297d

Please sign in to comment.