run ?priority ?thread ?name f runs
f () in another thread and returns the result
as a Deferred in the Async world. If
f () raises an exception (asynchronously,
since it is another thread) then that exception will be raised to the monitor that
Async code should not be used from within
thread is not supplied, then any thread from the thread pool could be used. If
you need to run routines in a specific thread (as is required by some libraries like
Sqlite), you should create a helper thread and supply it to
priority is supplied, the priority of the thread in the linux scheduler will be
priority for the duration of
f (), provided the thread is allowed to do so,
see `man setpriority`.
If you call
run several times with the same helper thread, the
f () calls will run
in sequence, in the order in which they are supplied to
f () will
complete (return or raise) before another
f () starts.
For example, if you do:
let () = run ~thread f1; run ~thread f2; run ~thread f3;
Then the thread will run
f1 () to completion, then
f2 () to completion, then
f3 () to completion.
name is supplied, the name of the thread will be set to it for the duration of
the execution of
when_finished describes how the helper thread behaves once
f () has completed:
`Take_the_lockit takes the Async lock and runs a cycle immediately
`Notify_the_schedulerit just notifies the scheduler that the result is ready
`Bestit tries to take the lock and run a cycle, but will fallback to
`Notify_the_schedulermethod if the Async lock is already held by someone else. The default is
`Best, and one shouldn't need to change it -- it is useful only for unit testing.
syscall f runs f, which should be a single system call, and returns the result,
handling the restarting of interrupted system calls. To avoid race conditions, the
f supplied to
syscall should just make a system call. That way, everything else
is done holding the Async lock.