C# ‘is’ operator performance

by

Using is can hurt performance if, once you check the type, you cast to that type. is actually casts the object to the type you are checking so any subsequent casting is redundant.

If you are going to cast anyway, here is a better approach:

ISpecialType t = obj as ISpecialType;

if (t != null)
{
    // use t here
}

More Related Contents:

  1. Performance surprise with “as” and nullable types
  2. Float vs Double Performance
  3. Is a LINQ statement faster than a ‘foreach’ loop?
  4. How do ValueTypes derive from Object (ReferenceType) and still be ValueTypes?
  5. Unloading the Assembly loaded with Assembly.LoadFrom()
  6. Excel Interop – Efficiency and performance
  7. Nullable type is not a nullable type?
  8. Is there a performance impact when calling ToList()?
  9. Performance Tests of Serializations used by WCF Bindings
  10. Performance of calling delegates vs methods
  11. HttpWebRequest is extremely slow!
  12. c# – Volatile keyword usage vs lock
  13. Efficient Cartesian Product algorithm
  14. sizeof(int) on x64?
  15. Static vs. non-static method
  16. C# quickest way to shift array
  17. System.Net.WebClient unreasonably slow
  18. How much faster is C++ than C#?
  19. Console.WriteLine slow
  20. Why does struct alignment depend on whether a field type is primitive or user-defined?
  21. How do I measure how long a function is running?
  22. Why only literal strings saved in the intern pool by default?
  23. How to read last “n” lines of log file [duplicate]
  24. variable scope in statement blocks
  25. When to change the Generate Serialization Assembly value?
  26. Setting properties via object initialization or not : Any difference ?
  27. Slow SoapHttpClientProtocol constructor
  28. Can you have multiple enum values for the same integer? [duplicate]
  29. Retrieve JIT output
  30. Why subsequent direct method call is much faster than the first call?

Leave a Comment