Skip to content

Commit e2f9807

Browse files
pockejonathanhefner
andcommitted
[CI skip] Add (see below) notations to threading documentation
Co-authored-by: Jonathan Hefner <[email protected]>
1 parent 39ceb5d commit e2f9807

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

guides/source/threading_and_code_execution.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ end
7272
```
7373

7474
TIP: If you repeatedly invoke application code from a long-running process, you
75-
may want to wrap using the Reloader instead.
75+
may want to wrap using the [Reloader](#reloader) instead.
7676

7777
Each thread should be wrapped before it runs application code, so if your
7878
application manually delegates work to other threads, such as via `Thread.new`
@@ -108,9 +108,10 @@ end
108108

109109
### Concurrency
110110

111-
The Executor will put the current thread into `running` mode in the Load
112-
Interlock. This operation will block temporarily if another thread is currently
113-
either autoloading a constant or unloading/reloading the application.
111+
The Executor will put the current thread into `running` mode in the [Load
112+
Interlock](#load-interlock). This operation will block temporarily if another
113+
thread is currently either autoloading a constant or unloading/reloading
114+
the application.
114115

115116
Reloader
116117
--------
@@ -320,4 +321,3 @@ backtrace.
320321
Generally a deadlock will be caused by the interlock conflicting with some other
321322
external lock or blocking I/O call. Once you find it, you can wrap it with
322323
`permit_concurrent_loads`.
323-

0 commit comments

Comments
 (0)