The MSDN documentation for the IsSubclassOf method states:
Determines whether the class represented by the current Type derives from the class represented by the specified Type.
Pretty useful, eh? However, it doesn’t work when it comes to interfaces:
The IsSubclassOf method cannot be used to determine whether an interface derives from another interface, or whether a class implements an interface.
Ok, roger that, but what about generics? Let’s see..
The MSDN documentation for the IsAssignableFrom method states:
Determines whether an instance of the current Type can be assigned from an instance of the specified Type.
The IsAssignableFrom method basically works the same way as the is operator and does a simple assignment compatibility test to see if a variable of type A can be assigned with a variable of type B. Unlike the IsSubclassOf method, it also works for interfaces and remember, if typeof(B).IsSubclassOf(typeof(A)) is true then typeof(A).IsAssignableFrom(typeof(B)) is also true.
Again, let’s consider the generics case:
In general, doing reflection is an expensive business and you should always be mindful of the potential performance hit you get if you have to do lots of reflection in your code.
I can’t think of too many places where you’d need to repeatedly test if one type is subclass of/can be assigned from another type but nonetheless, out of pure curiosity, I decided to give it a test and see what sort of performance overhead these two methods carry and here are the results:
Test: execute 100000 times
|Method call||Return value||Avg time taken (milliseconds) over 3 tries|
Notice that with the IsSubclassOf method there’s noticeable difference in average run time between cases that returns true and those that return false. Whilst the IsAssignableFrom method consistently runs at 6 milliseconds.
However, given the small amount of time taken to execute each check 100000 times the morale of this story is really “Don’t lose any sleep over it”!
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong