Why is this code invalid in C#?

c# nullable conditional-operator dbnull
mmattax picture mmattax · Oct 14, 2008 · Viewed 12.7k times · Source

The following code will not compile:

string foo = "bar";
Object o = foo == null ? DBNull.Value : foo;

I get: Error 1 Type of conditional expression cannot be determined because there is no implicit conversion between 'System.DBNull' and 'string'

To fix this, I must do something like this:

string foo = "bar";
Object o = foo == null ? DBNull.Value : (Object)foo;

This cast seems pointless as this is certainly legal:

string foo = "bar";
Object o = foo == null ? "gork" : foo;

It seems to me that when the ternary branches are of different types, the compiler will not autobox the values to the type object...but when they are of the same type then the autoboxing is automatic.

In my mind the first statement should be legal...

Can anyone describe why the compiler does not allow this and why the designers of C# chose to do this? I believe this is legal in Java...Though I have not verified this.

Thanks.

EDIT: I am asking for an understanding of why Java and C# handle this differently, what is going on underneath the scenes in C# that make this invalid. I know how to use ternary, and am not looking for a "better way" to code the examples. I understand the rules of ternary in C#, but I want to know WHY...

EDIT (Jon Skeet): Removed "autoboxing" tag as no boxing is involved in this question.

Answer

Jon Skeet picture Jon Skeet · Oct 14, 2008

The compiler requires that either the types of second and third operands are the same, or that one is implicitly convertible to the other. In your case, the types are DBNull and string, neither of which is implicitly convertible to the other. Casting either of them to object solves that.

EDIT: Looks like it is indeed legal in Java. Quite how it works out what to do when it comes to method overloading, I'm not sure... I've just looked at the JLS, and it's extremely unclear about what the type of the conditional is when there are two incompatible reference types involved. The C# way of working may be more irritating occasionally, but it's clearer IMO.

The relevant section of the C# 3.0 spec is 7.13, the conditional operator:

The second and third operands of the ?: operator control the type of the conditional expression. Let X and Y be the types of the second and third operands. Then,

  • If X and Y are the same type, then this is the type of the conditional
  • Otherwise, 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.
  • Otherwise, 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.

Related questions

Nullable types and the ternary operator: why is `? 10 : null` forbidden?

I just came across a weird error: private bool GetBoolValue() { //Do some logic and return true or false } Then, in another method, something like this: int? x = GetBoolValue() ? 10 : null; Simple, if the method returns true, assign 10 to the Nullableint x. …

Read More
Nullable type issue with ?: Conditional Operator

Could someone explain why this works in C#.NET 2.0: Nullable<DateTime> foo; if (true) foo = null; else foo = new DateTime(0); ...but this doesn't: Nullable<DateTime> foo; foo = true ? null : new DateTime(0); The latter form gives me …

Read More
Conditional operator assignment with Nullable<value> types?

EmployeeNumber = string.IsNullOrEmpty(employeeNumberTextBox.Text) ? null : Convert.ToInt32(employeeNumberTextBox.Text), I often find myself wanting to do things like this (EmployeeNumber is a Nullable<int> as it's a property on a LINQ-to-SQL dbml object where the column allows …

Read More