From 149297da143b563d8d4366d7f4074a3c4a475251 Mon Sep 17 00:00:00 2001 From: Julien Couvreur Date: Tue, 17 Sep 2024 11:10:18 -0700 Subject: [PATCH] Misplaced question mark for nullable value type conversion (#1176) --- standard/conversions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard/conversions.md b/standard/conversions.md index ef5d4cbff..6502b94ac 100644 --- a/standard/conversions.md +++ b/standard/conversions.md @@ -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) and [§10.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.