Why is NaN (not a number) only available for doubles?

by

Integral types in .NET use two’s complement system for representation. While they could reserve some bit patterns for special values, they chose not to. double and float use a completely different representation system (IEEE 754) which reserves some special bit patterns for NaN, +Infinity, -Infinity, …

One reason that NaN and Infinity values make more sense for floating point arithmetic is that operations could result division by zero, not only because the divisor is actually zero, but because it’s too small to be represented by the type. As a result, if that wasn’t the case, you could have some valid calculation mysteriously throw a divide by zero exception. This won’t happen for int types as they are exact and don’t have a precision error.

decimal is designed to be used for “real-world” decimal floating point numbers. It’s rarely subject to calculations that double and float are designed to do. What would NaN express for a real world number?

Leaving reasons behind it alone, it is what it is and there’s nothing we could do about it, so the best route to go is to use nullable types (they are designed to help with exactly this kind of situation). It’s the right way to solve this problem. If you don’t want to do that (and exceptions don’t make sense), you should resort to the magic number solution. If you chose to do so, just make sure it’s outside of the domain of valid results.

EDIT (very common misconception about decimal):

As also noted by MSDN, decimal is not fixed point. It is a floating point number:

A decimal number is a floating-point value that consists of a sign, a numeric value where each digit in the value ranges from 0 to 9, and a scaling factor that indicates the position of a floating decimal point that separates the integral and fractional parts of the numeric value.

More Related Contents:

  1. How to create a new object instance from a Type
  2. String was not recognized as a valid DateTime ” format dd/MM/yyyy”
  3. Integer summing blues, short += short problem
  4. How To Change DataType of a DataColumn in a DataTable?
  5. Generics in C#, using type of a variable as parameter [duplicate]
  6. What is cool about generics, why use them?
  7. Casting a variable using a Type variable
  8. Why do these division equations result in zero?
  9. C#: Overriding return types
  10. C# use System.Type as Generic parameter
  11. Why should I use int instead of a byte or short in C#
  12. .NET Integer vs Int16?
  13. Why is ushort + ushort equal to int?
  14. Using IsAssignableFrom with ‘open’ generic types
  15. .NET : How do you get the Type of a null object?
  16. How to cast Object to its actual type?
  17. Determine if a type is static
  18. What are the differences between value types and reference types in C#? [duplicate]
  19. Performing Math operations on decimal datatype in C#?
  20. cast object with a Type variable
  21. Why can’t Double be implicitly cast to Decimal
  22. How to switch between “possible” type of an object? [duplicate]
  23. What to do when bit mask (flags) enum gets too large
  24. Why does my C# array lose type sign information when cast to object?
  25. Are nullable types reference types?
  26. dynamic vs object type
  27. C#: Oracle Data Type Equivalence with OracleDbType
  28. How do I check if a type provides a parameterless constructor?
  29. Using various types in a ‘using’ statement (C#)
  30. Build c# Generic Type definition at runtime

Leave a Comment