Skip to content

Update overview-of-synchronization-primitives.md #53168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
TobiasKnauss wants to merge 1 commit into from
Closed

Update overview-of-synchronization-primitives.md #53168

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/standard/threading/overview-of-synchronization-primitives.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,13 @@ ms.assetid: b782bcb8-da6a-4c6a-805f-2eb46d504309

.NET provides a range of types that you can use to synchronize access to a shared resource or coordinate thread interaction.

> [!NOTE]

@BillWagner BillWagner Apr 27, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't help readers much. Instead, can you add even a brief section on System.Threading.Lock with the xref you have here, and a link to the C# language reference updates that show how the lock keyword behaves with the System.Threading.Lock type?

@TobiasKnauss TobiasKnauss Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does not help readers much because it does not provide the details that should be added here. But at least, it tells the reader that the list is no longer complete and other types exist, and that they need to look them up themselves until the docs are updated. So, it does help the readers somewhat.
I would love to update the docs, but I have not used this new type yet, so I cannot write anything useful about it. Maybe I will after having used it and when I find time for it, which is quite difficult at the moment and in the foreseeable future.

> PLEASE NOTE: This article was written in 2018. In the meanwhile, more synchronization primitives were developed, which are not yet described in this article:
>
> - <xref:System.Threading.Lock?displayProperty=nameWithType>
>
> Descriptions for these types will be added when this article is reworked.

> [!IMPORTANT]
> Use the same synchronization primitive instance to protect access of a shared resource. If you use different synchronization primitive instances to protect the same resource, you'll circumvent the protection provided by a synchronization primitive.

Expand Down
Loading