Skip to content

Commit 31e1bd5

Browse files
committed
Link to GotoIfNot in Julia docs
1 parent d29a722 commit 31e1bd5

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

src/copyable_task.jl

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -257,11 +257,12 @@ modified to ensure that whenever a `produce` call in encountered, the `MistyClos
257257
the argument to `produce`, and that subsequent calls resume computation immediately after
258258
the `produce` statement. This resumption is achieved by setting the value of a counter
259259
prior to returning following a `produce` statement -- a sequence of comparisons against this
260-
counter, and `goto-if-not` statement are inserted at the top of the IR. These are used to
261-
jump to the point in the code from which computation should resume. These are set up such
262-
that, when the `TapedTask` is first run, computation start froms the first statement.
263-
Observe that this is also facilitated by the ref mechanism
264-
discussed above, as it ensures that the state persists between calls to a `MistyClosure`.
260+
counter, and [`GotoIfNot`](https://docs.julialang.org/en/v1/devdocs/ast/#Lowered-form)
261+
statement are inserted at the top of the IR. These are used to jump to the point in the code
262+
from which computation should resume. These are set up such that, when the `TapedTask` is
263+
first run, computation start froms the first statement. Observe that this is also
264+
facilitated by the ref mechanism discussed above, as it ensures that the state persists
265+
between calls to a `MistyClosure`.
265266
266267
The above gives the broad outline of how `TapedTask`s are implemented. We refer interested
267268
readers to the code, which is extensively commented to explain implementation details.

0 commit comments

Comments
 (0)