mgravell / mgravell/PooledAwait
Is this make sense to be used with the latest .net frameworks?
Open
- Dominant language
- C#
- Stars
- 405
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
It seems .net team made a change in the latest .net frameworks https://github.com/dotnet/coreclr/pull/26310
which made `ValueTask` allocation free. I wonder if using PooledAwait make sense if you are using .net 5 or higher?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked CoreCLR pull request and comparing its allocation behavior with PooledAwait's stated approach. Determine whether PooledAwait provides benefits on .NET 5 or later, then document the supported framework versions and whether its use remains recommended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100