Hello Mauricio,
Thursday, November 29, 2007, 4:52:54 AM, you wrote:
> 'takeMVar' documentation says "if there are
consider MVar as one-slot channel with putMVar and takeMVar operations
for sending/receiving data
--
Best regards,
Bulatmailto:[EMAIL PROTECTED]
Maurício wrote:
Hi,
'takeMVar' documentation says "if there are
multiple threads blocked in takeMVar, and the
MVar becomes full, only one thread will be
woken up."
Since 'takeMVar' is a reading function, i.e.,
it doesn't change the value of the
"variable", why waking up only one thread? If
we
> 'takeMVar' documentation says "if there are
> multiple threads blocked in takeMVar, and the
> MVar becomes full, only one thread will be
> woken up."
>
> Since 'takeMVar' is a reading function, i.e.,
> it doesn't change the value of the
> "variable", why waking up only one thread? If
> we wake m
Hi,
'takeMVar' documentation says "if there are
multiple threads blocked in takeMVar, and the
MVar becomes full, only one thread will be
woken up."
Since 'takeMVar' is a reading function, i.e.,
it doesn't change the value of the
"variable", why waking up only one thread? If
we wake multiple thre
