0

Comparing unnamed data slots and ThreadLocal...

MSDN only says

In the .NET Framework 4, you can use the System.Threading.ThreadLocal class to create thread-local objects that are initialized lazily when the object is first consumed. For more information, see Lazy Initialization.

If I'm fine with lazy init, ThreadLocal seems like the best choice... it's simpler to use and doesn't require casting. Is there any other things to consider when choosing one over the other?

AfterWorkGuinness
  • 1,780
  • 4
  • 28
  • 47
  • 3
    On Windows, `ThreadLocal` is implemented using the Thread Local Dataslots API. Unless you have some compelling reason to work at the Windows API level, you're better off using `ThreadLocal`. – Jim Mischel Jun 08 '16 at 15:55

1 Answers1

2

As I said in comments, ThreadLocal<T> is implemented using the Thread Local Dataslots API. You can confirm that by looking at the ThreadLocal source code. Unless you have some compelling reason to work at the Windows API level, you're better off using ThreadLocal<T>.

One very good reason to choose ThreadLocal<T> is that it makes sure that the value is initialized for every thread. ThreadStatic does not do that, and your interface to thread local data slots API would have to code specially for it, too. See https://stackoverflow.com/a/18337158/56778 for a bit more info.

Use ThreadLocal<T> with lazy initialization. You'll save yourself a lot of pain.

Community
  • 1
  • 1
Jim Mischel
  • 131,090
  • 20
  • 188
  • 351