From ef92e1e43b6e385a6b38359af077333657de5b96 Mon Sep 17 00:00:00 2001 From: Mark Cilia Vincenti Date: Tue, 1 Oct 2024 10:28:27 +0200 Subject: [PATCH] Fixed documentation --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 62f8d2c..45cb1b1 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ A micro-library that backports/polyfill .NET 9.0+'s `System.Threading.Lock` to prior framework versions (from .NET Framework 3.5 up to .NET 8.0), providing as much backward compatibility as possible. ## Why is this useful? -Apart from streamlining locking, especially with a new [lock statement pattern](https://github.com/dotnet/csharplang/issues/7104) being proposed, and the ability to use the [`using` pattern for locking](https://learn.microsoft.com/en-us/dotnet/api/system.threading.lock.enterscope?view=net-9.0#system-threading-lock-enterscope), the more obvious reason for using it is that it gives greater performance than simply locking on an object. +Apart from streamlining locking, especially with a new [lock statement pattern](https://github.com/dotnet/csharplang/issues/7104) being proposed, and the ability to use the [`using` pattern for locking](https://learn.microsoft.com/en-us/dotnet/api/system.threading.lock.enterscope?view=net-9.0#system-threading-lock-enterscope), the more obvious reason for using it is that it gives greater performance (on .NET 9.0+) than simply locking on an object. ## Why not keep it simple? Some developers have opted to put in code like this: