Skip to content
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

Jump to bottom

Is this make sense to be used with the latest .net frameworks? #13

Open
ekalchev opened this issue Feb 20, 2022 · 1 comment
Open

Is this make sense to be used with the latest .net frameworks? #13

ekalchev opened this issue Feb 20, 2022 · 1 comment

Comments

@ekalchev
Copy link

It seems .net team made a change in the latest .net frameworks dotnet/coreclr#26310
which made ValueTask<T> allocation free. I wonder if using PooledAwait make sense if you are using .net 5 or higher?
@ekalchev ekalchev changed the title Is this still viable with latest .net frameworks? Is this make sense to be used with the latest .net frameworks? Feb 20, 2022
@Kaliumhexacyanoferrat
Copy link

Would be interesting for me to know as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Kaliumhexacyanoferrat @ekalchev