linksplatform / linksplatform/Threading
Do we really need ConcurrentQueueExtensions?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
.NET contains [`Task.WaitAll` method](https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.waitall), and it can be enough to use it. That also means that ConcurrentQueueExtensions can be deleted, as these methods promote a worse design than `Task.WaitAll` method.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for ConcurrentQueueExtensions and every caller, then read the relevant tests or examples alongside the .NET Task.WaitAll documentation. Determine whether the extension can be removed without breaking consumers; done means the maintainers have a clear deletion decision and any affected usages or tests are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100