You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 24, 2020. It is now read-only.
I've noticed 813fe1d and I decided to investigate this problem. I've focused on TestContinueWithUsingPrecedentTask.
After some debugging, I believe this problem is caused by two bugs:
The original AutoAsyncIssue has insufficient testing and fails for Tasks with no parameters that happen to be reused. I've added the missing test case and it also fails on Linux. See luiscubal@0f48a97
The resolver behaves differently on Windows. The lambda parameter in the continuation (precedent) resolves to Task<int>(correctly) on Linux but Task (incorrectly) on Windows. This triggered the untested code path for Tasks with no parameters on Windows.
This is all I've got for today. I'll take another look and try to fix 1 when I have some more time, but I'll have to rely on someone else to figure out the cause of problem 2. Should I start a separate issue for that one?