Export remotecall_eval
#123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@everywherehas (slightly surprising) behaviour forusing/importstatements that can best be avoided by usingremotecall_evaldirectly, so i thinkremotecall_evalshould be exported (or at least markedpublicbut i thinkexportis fine here.Context:
The behaviour of
@everywhereis that it tries to findusing/importstatements and run them on the calling process first, which means an@everywherecan't be defined inside a function if it contains ausing/import(unless you add a hack to cause@everywhereto not find yourusing/import).i.e. while this works
This fails:
An ugly hack to "hide" the
usingin a function call (lol this works):But a better solution is to just not use
@everywhere, since this is it's documented behaviour:and instead use
remotecall_evaljust as the docstring for@everywherementions, i.e.