Skip to content

docs: Document rationale for QueueWorkItem overloads #458

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

Merged
ZjzMisaka merged 1 commit into from
Apr 14, 2026
Merged

docs: Document rationale for QueueWorkItem overloads #458

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
10 changes: 10 additions & 0 deletions PowerThreadPool/Core/PowerThreadPool.QueueWorkItem.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,16 @@

namespace PowerThreadPool
{
/// <summary>
/// There are a great many overloads of QueueWorkItem, but this is the conventional .NET approach.
/// I want to keep the API strongly typed without introducing a source generator,
/// so I’m trading space for ease of use.
/// Considering that:
/// https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/Tuple.cs
/// https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/Action.cs
/// https://github.com/dotnet/runtime/blob/main/src/libraries/System.Private.CoreLib/src/System/Function.cs
/// all use a similar brute-force overloading pattern, I think this is unavoidable.
/// </summary>
public partial class PowerPool
{
private long _workIDIncrement = 0;
Expand Down
Loading