seb/XM_40017
1
0
Fork 0
mirror of https://github.com/fverdugo/XM_40017.git synced 2025-12-29 18:28:31 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

build based on c6c9aa9

Browse Source
This commit is contained in:
Documenter.jl
2024-09-23 12:01:25 +00:00
parent 038a80eea6
commit 468c8dd0ca
24 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
dev/julia_distributed_src/index.html
View File

@@ -8086,7 +8086,7 @@ a.anchor-link {
</div>
<div class="jp-InputArea jp-Cell-inputArea"><div class="jp-InputPrompt jp-InputArea-prompt">
</div><div class="jp-RenderedHTMLCommon jp-RenderedMarkdown jp-MarkdownOutput" data-mime-type="text/markdown">
<h3 id="@async-vs-@spawnat"><code>@async</code> vs <code>@spawnat</code><a class="anchor-link" href="#@async-vs-@spawnat"></a></h3><p>The relation between <code>@async</code> and <code>@pawnat</code> is obvious. From the user perspective they work almost in the same way. However, <code>@async</code> generates a task that runs asynchronously in the current process, whereas <code>@spawnat</code> executes a task in a remote process in parallel. In both cases, the result is obtained using <code>fetch</code>.</p>
<h3 id="@async-vs-@spawnat"><code>@async</code> vs <code>@spawnat</code><a class="anchor-link" href="#@async-vs-@spawnat"></a></h3><p>The relation between <code>@async</code> and <code>@spawnat</code> is obvious. From the user perspective they work almost in the same way. However, <code>@async</code> generates a task that runs asynchronously in the current process, whereas <code>@spawnat</code> executes a task in a remote process in parallel. In both cases, the result is obtained using <code>fetch</code>.</p>
</div>
</div>
</div>