Ordering in ReaderWriterLock

When I use lock(){...}, I cannot garantee which thread开发者_运维问答 will enter the lock first.

What about ReaderWriterLock? Does it works like a FIFO for the writers or not?

What about ReaderWriterLock? Does it works like a FIFO for the writers or not?

It does.

And you pay a performance penalty for this, which is why ReaderWriterLockSlim was introduced—less overhead but it isn't "fair".