We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It may be too convenient for the tasks to become a run away train if client developers do not use the await keyword upon their Interrupt method calls.
await
Interrupt
Let's keep track of all those tasks and ensure that the primary SceneActor keeps track of all the tasks.
SceneActor
Consider replacing the nested calls to a stack of some sort
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It may be too convenient for the tasks to become a run away train if client developers do not use the
await
keyword upon theirInterrupt
method calls.Let's keep track of all those tasks and ensure that the primary
SceneActor
keeps track of all the tasks.Consider replacing the nested calls to a stack of some sort
The text was updated successfully, but these errors were encountered: