Replies: 3 comments 4 replies
-
I guess some functions could have a long chain of dependencies that are built into the namespace that would all have to be re-created in the background process... |
Beta Was this translation helpful? Give feedback.
-
Previous discussion: I've tried every possible method/workaround to make the functions available on the background process but the only method that works is to define every single function explicitly in the code that will be run on the background process. Are there any workarounds you are aware of @HenrikBengtsson that we can use until this feature is added? I feel like we've reached an impasse in trying to go asynchronous with We have a request related to this that would really improve the way I've tried every possible method/workaround to make the functions available on the background process but the only method that works is to define every single function explicitly in the code that will be run on the background process. Are there any workarounds you are aware of @HenrikBengtsson that we can use until this feature is added? I feel like we've reached an impasse in trying to go asynchronous with
Hi @HenrikBengtsson, We have a function defined in the However, when This is
|
Beta Was this translation helpful? Give feedback.
-
Ok, reprex is ready:
SessionInfo
|
Beta Was this translation helpful? Give feedback.
-
Continued from #480
It doesn't sound like there are any workaround at present for this kind of issue. Is it feasible as a feature request to strip namespaces from functions passed to
globals
and create those functions in the environment on the background process?Beta Was this translation helpful? Give feedback.
All reactions