Currently they use asyncio.sleep to repeatedly poll for state changes. This works, but it does lead to unnecessary checks and can make the resolution order unpredictable. For instance if four tasks all try to write one after another you would want them to happen in order, but using the current scheme the first one will happen first but the rest of them will happen in a random order (whoever happens to run in the asyncio loop will go next).

The easiest fix here would probably be to use two asyncio.Lock instances, one for send and one for recv.

This isn't a huge priority or anything but it would make the code feel less hacky and help ensure the resolution order.