Is this a valid, lazy, thread-safe Singleton implementation for C#?
- by Matthew
I implemented a Singleton pattern like this:
public sealed class MyClass {
...
public static MyClass Instance {
get { return SingletonHolder.instance; }
}
...
static class SingletonHolder {
public static MyClass instance = new MyClass ();
}
}
From Googling around for C# Singleton implementations, it doesn't seem like this is a common way to do things in C#. I found one similar implementation, but the SingletonHolder class wasn't static, and included an explicit (empty) static constructor.
Is this a valid, lazy, thread-safe way to implement the Singleton pattern? Or is there something I'm missing?
