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
R3 Observable as UniTask never completes #576
Comments
if |
I see. I'd like to think about that conversion path, but semantically, |
Does this If yes then it is already good enough to bridge R3 and UniTask. But as I understand UniTask stands for optimization and integration into unity's player loop. When we first create Obviously R3 nor UniTask shouldn't know about each other, which is why we need some bridge. Guess separate package would be overkill for such little extension. Maybe some code gist would be enough for folks like me who want to use those packages in a tight couple. |
In R3, FirstAsync or LastAsync allows you to decide which way to wait. It is natural to want to convert R3 to an awaitable type (that is why FirstAsync and LastAsync exist). |
In R3 there is only
Observable
class so I can't use.ToUniTask()
directly, instead I try to use.AsSystemObservable
before but such code never completed. Observable query itself also works when subscribed with classic R3.Subscribe
method. At the same time simpleDelay
works perfectly. Am I doing something wrong or there is no way to treat R3 observable as UniTask?Unity 2023.2.15
R3 1.1.11
UniTask 2.5.4
The text was updated successfully, but these errors were encountered: