J Jon Skeet [C# MVP] Jul 19, 2004 #2 Joel said: Is there a run-time performance cost for casting? Click to expand... Yes, but it's very small. How many casts are you thinking of doing?
Joel said: Is there a run-time performance cost for casting? Click to expand... Yes, but it's very small. How many casts are you thinking of doing?
J Joel Wilson Jul 19, 2004 #3 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.
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.
J Jon Skeet [C# MVP] Jul 19, 2004 #4 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. Click to expand... 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.
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. Click to expand... 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.
