Couldn't help but wonder as to why you made the proc function async? I ran this bit of code with and without it, but spotted no real difference. Just something eating away at my curiosity.
My "bad", it's a carryover from my other, simpler, comment.
There, awaiting proc was the single yield point in the loop, so it did make all the difference. Here there's a second await from the pull inside the loop iteration, so processing can be made sync.
However, and yet again my bad, it seems awaiting a sync value still yields to the event loop as well. So in both examples it is unnecessary.
I'll now edit both comments accordingly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Couldn't help but wonder as to why you made the proc function async? I ran this bit of code with and without it, but spotted no real difference. Just something eating away at my curiosity.
My "bad", it's a carryover from my other, simpler, comment.
There, awaiting
procwas the single yield point in the loop, so it did make all the difference. Here there's a second await from thepullinside the loop iteration, so processing can be made sync.However, and yet again my bad, it seems
awaiting a sync value still yields to the event loop as well. So in both examples it is unnecessary.I'll now edit both comments accordingly.