-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return values from coroutines #7
Comments
In 1.6 the next best thing you can do is I'm not willing to mark an engine type as a coroutine, that would break a lot of things. I have experimented with a |
Ok, I just want to say: it's would be very useful stuff, especailly with TTuple. Also I think we can always make USTRUCT child from templated TAsyncCoroutine. And it seems lot of code with coroutines should use UFUNCTIONs rarely. (I wish templated objects will be supported by UHT. They made possibility to add custom plugins, will see...) |
1.7 will add support for |
Sometimes, when I awaited some data, for example of async loading of resources. I need return it from my coroutine. The best thing that comes to mind is using TTask with co_return. Can you add support for this?
For example:
But TTask is not awaitable? Maybe add new type of task, like
TCoroTask
?The text was updated successfully, but these errors were encountered: