performs same check and in this code it’s not atomic, so it’s possible to
await
deferred in
Completed
state after checking for
!isCompleted
.
Check doesn’t improve neither readability nor performance
u
uli
04/20/2018, 8:14 AM
I know it's broken. But the idea was to not await any deferreds that have already been awaited. I'll check the solution from issue 171 you mentioned below