Performance cost of casting

  • Thread starter Thread starter Joel
  • Start date Start date
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.
 
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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top