Operator “>” cannot be applied to type ‘ulong’ and ‘int’

by

I’ve been experimenting with this, using ILSpy to examine the output, and this is what I’ve discovered.

Obviously in your second case this is an error – you can’t compare a ulong and an int because there isn’t a type you can coerce both to. A ulong might be too big for a long, and an int might be negative.

In your first case, however, the compiler is being clever. It realises that const 1 > const 32 is never true, and doesn’t include your if statement in the compiled output at all. (It should give a warning for unreachable code.) It’s the same if you define and use a const int rather than a literal, or even if you cast the literal explicitly (i.e. (int)32).

But then isn’t the compiler successfully comparing a ulong with an int, which we just said was impossible?

Apparently not. So what is going on?

Try instead to do something along the following lines. (Taking input and writing output so the compiler doesn’t compile anything away.)

const int thirtytwo = 32;
static void Main(string[] args)
{
    ulong x = ulong.Parse(Console.ReadLine());
    bool gt = x > thirtytwo;
    Console.WriteLine(gt);
}

This will compile, even though the ulong is a variable, and even though the result isn’t known at compile time. Take a look at the output in ILSpy:

private static void Main(string[] args)
{
    ulong x = ulong.Parse(Console.ReadLine());
    bool gt = x > 32uL;        /* Oh look, a ulong. */
    Console.WriteLine(gt);
}

So, the compiler is in fact treating your const int as a ulong. If you make thirtytwo = -1, the code fails to compile, even though we then know that gt will always be true. The compiler itself can’t compare a ulong to an int.

Also note that if you make x a long instead of a ulong, the compiler generates 32L rather than 32 as an integer, even though it doesn’t have to. (You can compare an int and a long at runtime.)

This points to the compiler not treating 32 as a ulong in the first case because it has to, merely because it can match the type of x. It’s saving the runtime from having to coerce the constant, and this is just a bonus when the coercion should by rights not be possible.

More Related Contents:

  1. Check if the two Files exist in the folder
  2. How to write Unicode characters to the console?
  3. Calculate MD5 checksum for a file
  4. Cannot delete directory with Directory.Delete(path, true)
  5. Detect Windows version in .NET
  6. Difference between ref and out parameters in .NET [duplicate]
  7. Why does Boolean.ToString output “True” and not “true”
  8. ‘using’ statement vs ‘try finally’
  9. Implicit typing; why just local variables?
  10. How to change symbol for decimal point in double.ToString()?
  11. method overloading vs optional parameter in C# 4.0 [duplicate]
  12. STAThread and multithreading
  13. How to find the 3rd Friday in a month with C#?
  14. If strings are immutable in .NET, then why does Substring take O(n) time?
  15. string.ToLower() and string.ToLowerInvariant()
  16. The call stack does not say “where you came from”, but “where you are going next”?
  17. How to split csv whose columns may contain comma
  18. Populate TreeView with file system directory structure
  19. How can I data bind a list of strings to a ListBox in WPF/WP7?
  20. .Include() vs .Load() performance in EntityFramework
  21. How do I prevent a WCF service from enter a faulted state?
  22. Is there a .NET equivalent to SQL Server’s newsequentialid()
  23. Directly modifying List elements
  24. Regex for Money
  25. Convert Kinect ColorImageFrame to Bitmap
  26. How to get the Properties of a *.mp3 File in C#
  27. Retrieve List of Tables in MS Access File
  28. DataGridView Image for Button Column
  29. Where is the .NET JIT-compiled code cached?
  30. Run async method 8 times in parallel

Leave a Comment