Add support for `async/await` about rspotify HOT 10 CLOSED

As for ongoing plan to support async/await, I have talked with the author of spotify-tui on this PR, and everything is working in process now. Because my full time job is so damn busy, I have to take some extra time to support async/await, so please be patient :)

from rspotify.

Sorry, i did not mean to rush you.
Understood. I'm looking forward to it. I would like to be helpful for it if I can.

from rspotify.

I think your work/branch is inspired, there are a lot of things I could learn from your work. I just push my WIP work to remote origin. Instead of creating a nonblocking package, I prefer to create a blocking package, and make nonblocking default.

from rspotify.

I would like to be helpful for it if I can.

If you have time, you could help me to convert those endpoint functions to async/await version, I just update the internal functions to async, there are still a lot of endpoint functions that needs to update.

from rspotify.

will do.

from rspotify.

I just submit all the work Rspotify needs to do to support async/await, if you have time to join me, feel free to check it The workload of adding support for async/await

from rspotify.

I started to modify endpoint functions to support async/await in client.rs. I will send PR when i finished to implement them. Please wait.

from rspotify.

Perhaps you could send a new PR once you have finished to implement a endpoint function, or you could mark which endpoint function you are going to modify? just in case of any conflicting situation that we are both modifying the same endpoint function.

from rspotify.

oh, it has already been implemented.

from rspotify.

Rspotify has come to async/await, it's done.

from rspotify.