Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GpuFuture and Future #1412

Closed
timothee-haudebourg opened this issue Aug 23, 2020 · 2 comments · Fixed by #2051
Closed

GpuFuture and Future #1412

timothee-haudebourg opened this issue Aug 23, 2020 · 2 comments · Fixed by #2051

Comments

@timothee-haudebourg
Copy link

Hi,

I was wondering if you had any plans on making the GpuFuture trait compatible with the now standard Future trait? Being able to use async/await with vulkano would be great.

@Eliah-Lakhin
Copy link
Contributor

@timothee-haudebourg Hi!

I didn't hear if someone is planning to implement something like this, but I think it would be a good idea. You can start working on the featue.

There are a lot of open questions on how to make the interoperability between the CPU concurrent model and Vulkan GPU concurrent model transparent from the API design point of view. But probably this is doable. I have a wrapper in my personal project(still in a private repo) that makes such interoperability with Tokio, but for only a few cases specific to the project's domain. However, I think it could be extended to a general case.

@Eliah-Lakhin
Copy link
Contributor

Maybe as a first prototype solution you can make a Future trait wrapper around the existing GpuFuture API to persist the API back-compatibility.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants