You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we trigger walker's ability synchronously. But in theory, walker's ability is technically a entry to a process.
Right now the behavior is
spawn_call -> visit the first ability the correspond to first node -> run the ability -> queue the nodes that needs to visit -> visit the ability correspond to the next node
in background, it will still run synchronously however, it will be triggered something like this
enter1(root);
ifiscoroutine(res:=enter2(a)):
# open a thread to have isolated eventloop to run `res`# wait until it's finished before going to next flow
in this approach, we can support async flows, libraries or modules
The text was updated successfully, but these errors were encountered:
Currently, we trigger walker's ability synchronously. But in theory, walker's ability is technically a entry to a process.
Right now the behavior is
spawn_call -> visit the first ability the correspond to first node -> run the ability -> queue the nodes that needs to visit -> visit the ability correspond to the next node
in background, this will trigger
enter1(root) -> enter2(a)
synchronouslyhow about we support creating event loop to support asynchronous flow
in background, it will still run synchronously however, it will be triggered something like this
in this approach, we can support async flows, libraries or modules
The text was updated successfully, but these errors were encountered: