If there is an interface that both temporal server and client has not implemented yet, like for example listing workflow types by namespace, how do you suggest I should provide it?
`Selector` is meant to replace the normal `select` statements in workflow code. Temporal workflows support usual `defer` semantics and can be used like a normal Go function. They are not combined together.
If only there was a Python demo! The unofficial one needs some love too!
Here's a Python intro: th-cam.com/video/jZgtiGgEK6A/w-d-xo.html and docs: docs.temporal.io/dev-guide/python
@@Temporalio Thank You!
Very informative presentation. Thanks
If there is an interface that both temporal server and client has not implemented yet, like for example listing workflow types by namespace, how do you suggest I should provide it?
Don’t get it… select is select and defer is defer, why did they combine these two functionalities into one “selector” function
`Selector` is meant to replace the normal `select` statements in workflow code. Temporal workflows support usual `defer` semantics and can be used like a normal Go function. They are not combined together.
@@loren-sr 17:10 hm.. He said "AddFuture is kind of like defer statement" and that's why I thought they combined it.
Great explanations, but so fast speaking...