Update Future Objects to improve speed.

[Vizonex]

What do these changes do?

This change implements a new await-able container that I've tested with other outside methods and then brought the object over here when stress testing was complete. It is likely to replace asyncio.Future soon as it's an annoying bottleneck with winloop that is preventing it from reaching it's true speeds (especially with sockets).

Are there changes in behavior for the user?

Is it a substantial burden for the maintainers to support this?

Related issue number

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes

[Vizonex]

@fantix Sorry for the ping but I wanted you and the other uvloop maintainers to know that Cythonized await-able Future objects might be a good idea to try and start implementing, I've taken notes on these improvements 6 months ealrier and seems my wish has finally come true and it seems the tests have ran a lot quicker on my end (possibly shaving over a minute which is impressive). I'll let you guys copy and paste all of this code I am sharing as well as find new ways to optimize it recasting should eliminate some common networking bottlenecks with sockets and possibly a handful of other functions.

I may not have time to write another Pull request to Uvloop's end just yet as I am busy with my IRL job which is why I'm pinging. Otherwise maybe on Friday if I'm not drowning in other things will I make the PR myself.

If anything changes with the other code I will be syncing it back on my end if the code is somehow better than my own.

[fantix]

That sounds so cool, thank you for your patience!

[Vizonex]

That sounds so cool, thank you for your patience!

Your welcome I hope this idea serves the uvloop community well.