Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Should enumerable tasks default to one-at-a-time?
See original GitHub issueInstead of today being Task.WhenAll. It seems this default causes more problems than it solves. See #288
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Transform IEnumerable<Task<T>> asynchronously by ...
I'd like to transform my list of Tasks without the foreach, however either the anonymous function syntax nor the usual function syntax allows...
Read more >Async Enumerable in C# (Part 3)
This is a sensible default particularly if your tasks are CPU bound, as there would be no point going any higher. But there...
Read more >Dreaming of multiple tasks | Jon Skeet's coding blog
So let's just give it anything – the default value, for example. Then we've got two tasks which we can await together using...
Read more >Developers using JsonSerializer can asynchronously (de) ...
This tiny test app shows that JsonSerializer will stream an IEnumerable just fine -- the IEnumerable in question, ...
Read more >How Async/Await Really Works in C# - .NET Blog
Every time you wanted to write a reusable method that would consume another asynchronous operation, you'd need to do all of this work....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@sm-g pushed today, 5.1.0
@jbogard Could you publish nuget with recent changes (without
Task.WhenAll)? I think that could be reason of