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
It will be nice to have an option to execute jldoctest blocks in an external, spawned process. This would be an alternate option to wrapping the code block in a module before execution. Will help in addressing issues like JuliaLang/Distributed.jl#19 . stdout of the spawned process can be used to check for correctness.
The text was updated successfully, but these errors were encountered:
Definitely something we could consider. Should be a non-default option of a doctest I think. It will make the doctest execution much slower. Is there some API that would allow us to spawn a child Julia REPL session or something? Or should it be done with run?
Not very high priority though, so implementation is up for grabs.
It will be nice to have an option to execute jldoctest blocks in an external, spawned process. This would be an alternate option to wrapping the code block in a module before execution. Will help in addressing issues like JuliaLang/Distributed.jl#19 .
stdout
of the spawned process can be used to check for correctness.The text was updated successfully, but these errors were encountered: