I have always been a friendly competitor to other libraries and I think it's time this library tries to implement compiled Future objects as shown by the success of this pull request to winloop. Currently I do not have the time on my hands to do such a task yet as I have been either sick or busy. This shouldn't be too difficult as outlined in the Pull request referenced. Vizonex/Winloop#164 There is also an idea for Task objects that utilizes UVAsync to move coroutine frames along instead of needing to call Loop.call_soon every time which has always been ineffective and costly. I have seen great success rates with dns calls by making these changes and maybe along the way many other things can be further optimized by these ideas.
I have always been a friendly competitor to other libraries and I think it's time this library tries to implement compiled
Futureobjects as shown by the success of this pull request to winloop. Currently I do not have the time on my hands to do such a task yet as I have been either sick or busy. This shouldn't be too difficult as outlined in the Pull request referenced. Vizonex/Winloop#164 There is also an idea forTaskobjects that utilizesUVAsyncto move coroutine frames along instead of needing to callLoop.call_soonevery time which has always been ineffective and costly. I have seen great success rates with dns calls by making these changes and maybe along the way many other things can be further optimized by these ideas.