Is this a correct reentrant async lock?

This page summarizes the projects mentioned and recommended in the original post on /r/dotnet
#C# #Async #Await #asyncex #async-await

Our great sponsors
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Mergify - Updating dependencies is time-consuming.
  • SonarQube - Static code analysis for 29 languages.
Our great sponsors

  • cs-reentrant-async-lock

    A reentrant asynchronous lock

    But is it correct? I have several automated tests that no other implementation (that I know of) can pass: https://github.com/matthew-a-thomas/cs-reentrant-async-lock/blob/main/ReentrantAsyncLock.Tests/ReentrantAsyncLockClass.cs

  • AsyncEx

    A helper library for async/await.

    Re-entrant async locks are not possible with this library. See: https://github.com/StephenCleary/AsyncEx/blob/master/doc/AsyncLock.md

  • InfluxDB

    Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts