Question

A while back I wanted to create my own data mapper that would be much simpler than your average ORM. In doing so I found the need to have access to the type information of inheriting classes in my base class. My first thought was reflection, but it’s too slow (if you use reflection though, check out Fasterflect as it ‘almost’ eliminates the performance problems of reflection).

So I turned to a solution that I later found out had it’s own name: The Curiously Recurring Template Pattern. This mostly solved my problem, but learning how to correctly implement this pattern was a little challenging. The two main questions I had to solve were:

1) How can I let my consuming code work with my generic objects without needing to know the generic parameters the objects were created with?

2) How can I inherit static fields in C#?

The challenging part was actually figuring out the questions. Once I realized what I needed to do, solving these questions was pretty easy. If you find yourself in need of the CRTP, you will likely find yourself needing to answer these questions… they seem to go hand in hand.

Answer 1

Working with generics without knowing the generic parameter types

When using the CRTP it’s good to have a non-generic base class (abstract if possible, but that’s not too important) that your ‘base’ generic class inherits from. Then you can make abstract (or virtual) functions on your non-generic base class and allow consuming code to work with your objects without having to know the generic parameters. For example:

abstract class NonGenBase
{
    public abstract void Foo();
}

class GenBase<T>: NonGenBase
{
    public override void Foo()
    {
        // Do something
    }
}

Now consuming code that has no knowledge of what T is supposed to be can still call the Foo() procedure on your objects by treating them as instances of the base class.

How to solve the static field inheritance problem

When using the CRTP to solve a problem, it’s often beneficial to provide access to static fields in inheriting classes. The problem is that C# doesn’t allow inheriting classes to have access to those static fields, except through the type name… which often seems to defeat the purpose in this situation. You may not be able to think of a clear example of what I’m talking about and explaining one is beyond the scope of this answer, but the solution is simple so just tuck it away in your knowledgebase and when you find a need for it you’ll be glad it’s there 🙂

class GenBase<T>: NonGenBase
{
    static object _someResource;

    protected object SomeResource { get { return _someResource; } }
}

This ‘simulates’ inheritance of static fields. Keep in mind, however, that static fields on a generic class are not scoped across all your generic implementations. Each generic implementation has its own instance of the static field. If you want a single static field that is available to all the implementations, then you simply need to add it to your non-generic base class.