Skip to content

Commit

Permalink
Fix kill-thread description in threads.scrbl
Browse files Browse the repository at this point in the history
Like thread-suspend, kill-thread fails if it is managed by a custodian that is not current-custodian or one of its subordinates.  This new kill-thread description is based on the phrasing already used for the thread-suspend description.
  • Loading branch information
gregr authored and mflatt committed Apr 23, 2024
1 parent fee1bcb commit bdfaf67
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions pkgs/racket-doc/scribblings/reference/threads.scrbl
Original file line number Diff line number Diff line change
Expand Up @@ -149,10 +149,10 @@ Terminates the specified thread immediately, or suspends the thread if
@racket[thd] was created with
@racket[thread/suspend-to-kill]. Terminating the main thread exits the
application. If @racket[thd] has already terminated,
@racket[kill-thread] does nothing. If the @tech{current custodian}
does not manage @racket[thd] (and none of its subordinates manages
@racket[thd]), the @exnraise[exn:fail:contract], and the thread is not
killed or suspended.
@racket[kill-thread] does nothing. If the @tech{current custodian}
does not solely manage @racket[thd] (i.e., some custodian of @racket[thd]
is not the current custodian or a subordinate), the
@exnraise[exn:fail:contract], and the thread is not killed or suspended.

Unless otherwise noted, procedures provided by Racket (and GRacket) are
kill-safe and suspend-safe; that is, killing or suspending a thread
Expand Down

0 comments on commit bdfaf67

Please sign in to comment.