J
Joel
Is there a run-time performance cost for casting?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Jon Skeet [C# MVP]
Joel said:Is there a run-time performance cost for casting?
Yes, but it's very small. How many casts are you thinking of doing?
J
Joel Wilson
It's more of an academic question of casting vs. Convert.To(). I assume
the "small" performance hit is a typecheck on the object being cast.
the "small" performance hit is a typecheck on the object being cast.
J
Jon Skeet [C# MVP]
Joel Wilson said:It's more of an academic question of casting vs. Convert.To(). I assume
the "small" performance hit is a typecheck on the object being cast.
Yes. Using the "as" operator (for reference types) is marginally faster
in the current CLR, and certainly using "as" and then a nullity check
is faster than "is" and then a cast, but most of the time it shouldn't
have any significant impact.