Unexpected branches reported for async lambda expression
See original GitHub issueIn PR https://github.com/tonerdo/coverlet/pull/583 we fixed the issue with false line coverage for lambda.
Now we report a correct line coverage, but we’ve unexpected uncovered branches reported.
We should try to avoid to report compiler generated branches.
Test name Lambda_Issue343
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Unexpected branches reported for async lambda expression
In PR #583 we fixed the issue with false line coverage for lambda. Now we report a correct line coverage, but we've unexpected...
Read more >The 'await' operator can only be used within an async ...
The 'await' operator can only be used within an async lambda expression · 3. The lambda delegate is not marked as async (command)...
Read more >Let's dive into async/await in C#: Part 3
Await is missing for an asynchronous lambda method. This is a fairly serious bug because it is very easy to overlook in your...
Read more >4. Writing Async Methods - Async in C# 5.0 [Book]
In terms of C# syntax, await acts as a unary operator, like the ! not operator, or the ( type ) cast operator....
Read more >Stretching Async/Await With Lambdas
Both versions of the pipeline executes all fetch operations concurrently and after all requests have been dispatched it will accumulate the body ...
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 FreeTop 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
Top GitHub Comments
I agree, should be solved
That’s okay, I believe you – I’ll just wait 👍