Type of conditional expression cannot be determined because there is no implicit conversion between ‘int’ and

by

The spec (§7.14) says that for conditional expression b ? x : y, there are three possibilities, either x and y both have a type and certain good conditions are met, only one of x and y has a type and certain good conditions are met, or a compile-time error occurs. Here, “certain good conditions” means certain conversions are possible, which we will get into the details of below.

Now, let’s turn to the germane part of the spec:

If only one of x and y has a type, and both x and y are implicitly convertible to that type, then that is the type of the conditional expression.

The issue here is that in

int? number = true ? 5 : null;

only one of the conditional results has a type. Here x is an int literal, and y is null which does not have a type and null is not implicitly convertible to an int1. Therefore, “certain good conditions” aren’t met, and a compile-time error occurs.

There are two ways around this:

int? number = true ? (int?)5 : null;

Here we are still in the case where only one of x and y has a type. Note that null still does not have a type yet the compiler won’t have any problem with this because (int?)5 and null are both implicitly convertible to int? (§6.1.4 and §6.1.5).

The other way is obviously:

int? number = true ? 5 : (int?)null;

but now we have to read a different clause in the spec to understand why this is okay:

If x has type X and y has type Y then

  • If an implicit conversion (§6.1) exists from X to Y, but not from Y to X, then Y is the type of the conditional expression.

  • If an implicit conversion (§6.1) exists from Y to X, but not from X to Y, then X is the type of the conditional expression.

  • Otherwise, no expression type can be determined, and a compile-time error occurs.

Here x is of type int and y is of type int?. There is no implicit conversion from int? to int, but there is an implicit conversion from int to int? so the type of the expression is int?.

1: Note further that the type of the left-hand side is ignored in determining the type of the conditional expression, a common source of confusion here.

More Related Contents:

  1. How to check if an object is nullable?
  2. What is the difference between Nullable.HasValue or Nullable != null?
  3. Nullable type issue with ?: Conditional Operator
  4. What does “DateTime?” mean in C#?
  5. How to parse a string into a nullable int
  6. How to convert C# nullable int to int
  7. Compare nullable types in Linq to Sql
  8. C# nullable string error
  9. .NET – Convert Generic Collection to DataTable
  10. How can I format a nullable DateTime with ToString()?
  11. Nullable reference types: How to specify “T?” type without constraining to class or struct
  12. Ternary operator VB vs C#: why resolves Nothing to zero? [duplicate]
  13. ? (nullable) operator in C# [duplicate]
  14. Why is this code invalid in C#?
  15. Linq query with nullable sum
  16. Invalid cast from ‘System.Int32’ to ‘System.Nullable`1[[System.Int32, mscorlib]]
  17. Optional return in C#.Net
  18. Where in memory are nullable types stored?
  19. Why does .ToString() on a null string cause a null error, when .ToString() works fine on a nullable int with null value?
  20. Check inside method whether some optional argument was passed
  21. Best way to check for nullable bool in a condition expression (if …) [closed]
  22. Type result with conditional operator in C#
  23. Are nullable types reference types?
  24. What is the default value of the nullable type “int?” (including question mark)?
  25. Correct way to check if a type is Nullable [duplicate]
  26. What does exclamation mark mean before invoking a method in C# 8.0? [duplicate]
  27. What’s the difference between ‘int?’ and ‘int’ in C#?
  28. Serializing a Nullable in to XML
  29. Why doesn’t the conditional operator correctly allow the use of “null” for assignment to nullable types? [duplicate]
  30. how are nullable types implemented under the hood in .net?

Leave a Comment