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
I think quite often one just wants to initialize all ports/processes. Currently, this can not be done programmatically, as these are distinct fields/methods in the Context object. It would be good if we could either loop over them (maybe with a closure?) and/or just ctx.create_all_periodic_processes().
The text was updated successfully, but these errors were encountered:
I am also missing something like this. The issue is that the names of the ports are generated, so it is not possible to iterate through them at the use-site of the proc-macro. I was thinking about initializing all ports by default, if no start macro is called, but this is non-obvious behaviour. I dislike the idea of having a function that does the initialization of all available resources for a similar reason. What if you initialize some of the ports and then call the function. Would we attempt to recreate them? What does the APEX say about creating ports twice? Should this be idempotent or should the previous ref to the port object be overwritten?
I still fancy the idea of no start function. I am against auto initialization if no start function is defined, but if the start function would be empty anyways, it could just be omitted
I think quite often one just wants to initialize all ports/processes. Currently, this can not be done programmatically, as these are distinct fields/methods in the Context object. It would be good if we could either loop over them (maybe with a closure?) and/or just
ctx.create_all_periodic_processes()
.The text was updated successfully, but these errors were encountered: