From 91932bcfa539a807e6b5c7327865bcf1d3dd7d91 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Thu, 29 Sep 2016 17:37:09 -0400 Subject: [PATCH] Clarify cv's are allocated on the heap --- docs/api/srfi/18.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/srfi/18.md b/docs/api/srfi/18.md index 6dfacee2..c14d2a42 100644 --- a/docs/api/srfi/18.md +++ b/docs/api/srfi/18.md @@ -71,7 +71,7 @@ Unlock the given mutex. If there are threads waiting on the mutex, one of those Determine if the given object is a condition variable. #make-condition-variable (make-condition-variable) -Create a new condition variable. +Create a new condition variable. Like mutex objects, condition variables are always allocated directly on the heap since they are expected to be shared by more than one thread. #condition-variable-wait! (condition-variable-wait! condition-variable mutex) Wait on a condition variable. The mutex must be locked by the calling thread, and will be locked upon successful return of this function.