From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Concurrent MVars for Guile
Date: Thu, 16 Jan 2014 14:01:00 +0100 [thread overview]
Message-ID: <87a9ewaxo3.fsf@gnu.org> (raw)
In-Reply-To: <87zjmwrbv3.fsf@netris.org> (Mark H. Weaver's message of "Wed, 15 Jan 2014 19:47:44 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Andy Wingo <wingo@pobox.com> writes:
>
>> On Sat 14 Sep 2013 15:59, ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> It looks like a useful tool to me.
>>
>> FWIW I totally agree!
>>
>>> I don’t like the name “mvar” (“monadic variable”, I guess). Perhaps
>>> “synchronized box”, or “transactional variable”, or...? The downside of
>>> choosing another name is that people familiar with the concept won’t
>>> recognize it first-hand.
>>
>> I guess I can see this. I prefer "box" to "variable" fwiw. How about
>> "tbox"? (The T for threadsafe or transactional or something; perhaps
>> this is a bad idea.)
>
> My preference would be to keep the "mvars" name, however imperfect,
> simply because many people in the neighboring Haskell community already
> know them as "mvars".
OK, I think that makes sense then (I’ve seen mvars mentioned in various
places in the meantime.)
Hopefully the manual will make it clear what this is about. ;-)
Ludo’.
next prev parent reply other threads:[~2014-01-16 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 7:55 Concurrent MVars for Guile Mark H Weaver
2013-09-03 11:55 ` Mark H Weaver
[not found] ` <CAGua6m3o_NexANbGuDYd5_rbPQqsbXkK504ONaFE7PGdQd98og@mail.gmail.com>
2013-09-04 6:27 ` Fwd: " Stefan Israelsson Tampe
2013-09-05 2:10 ` David Thompson
2013-09-05 2:53 ` Mark H Weaver
2013-09-14 13:59 ` Ludovic Courtès
2013-09-17 20:18 ` Andy Wingo
2014-01-16 0:47 ` Mark H Weaver
2014-01-16 13:01 ` Ludovic Courtès [this message]
2014-01-17 6:33 ` Mateusz Kowalczyk
2014-01-17 19:31 ` Mark H Weaver
2014-01-18 0:46 ` Mark H Weaver
2014-01-18 1:05 ` Mateusz Kowalczyk
2014-01-21 5:38 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9ewaxo3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).