Shorthand if + nullable types (C#)

Question

The following returns

Type of conditional expression cannot be determined because there is no implicit conversion between 'double' and '<null>'

aNullableDouble = (double.TryParse(aString, out aDouble)?aDouble:null)

---

The reason why I can't just use aNullableBool instead of the roundtrip with aDouble is because aNullableDouble is a property of a generated EntityFramework class which cannot be used as an out par.

Answer 1

aNullableDouble = (double.TryParse(aString, out aDouble)?new Nullable<double>(aDouble):null)

Answer 2

aNullableDouble = double.TryParse(aString, out aDouble) ? (double?)aDouble : null;

Answer 3

Just blow the syntax out into the full syntax instead of the shorthand ... it'll be easier to read:

aNullableDouble = null;
if (double.TryParse(aString, out aDouble))
{
    aNullableDouble = aDouble;
}

Answer 4

.NET supports nullable types, but by declaring them as such you have to treat them a bit differently (as, understandably, something which is normally a value type now is sort of reference-ish).

This also might not help much if you end up having to do too much converting between nullable doubles and regular doubles... as might easily be the case with an auto-generated set of classes.

Answer 5

Put me on a stick and call me charly :s
That, my kind sirs, was a stupid mistake of mine. I was looking why it wanted to be able to cast the true return and the false return. Whilst off course I should have been looking at the cast from both returns to my aNullableDouble :P

Calls for a coffee brake I guess.

Answer 6

The interesting side-effect of using nullable types is that you can't really use a shorthand IF. Shorthand IF has to return the same Type from both conditions, and it can't be null in either case. So, cast or write it out :)