From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: ice-9 async-queue
Date: Tue, 7 Feb 2012 18:02:41 +0800 [thread overview]
Message-ID: <CAN3veRfSY29+zHLXNmfky+1qxoztF-MZgGRdgh_PDBF06qGbiw@mail.gmail.com> (raw)
In-Reply-To: <87d39rhp6i.fsf@pobox.com>
> async-queue-push!
> async-queue-pop! async-queue-try-pop!))
Note that these verbs conflict with those defined in (ice-9 q) where
"push" adds elements to the front, not the rear, of the queue.
This is a very tidy implementation. I presume the final version will
include a type and empty-ness predicate also?
Thanks
next prev parent reply other threads:[~2012-02-07 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 17:00 ice-9 async-queue Andy Wingo
2012-02-06 22:09 ` Mike Gran
2012-02-07 8:34 ` Andy Wingo
2012-02-07 8:36 ` Andy Wingo
2012-02-06 22:57 ` Ludovic Courtès
2012-02-07 8:44 ` Andy Wingo
2012-02-08 13:44 ` Ludovic Courtès
2012-03-03 17:53 ` Andy Wingo
2012-03-07 21:11 ` Ludovic Courtès
2012-02-07 10:02 ` Daniel Hartwig [this message]
2012-02-07 21:46 ` Andy Wingo
2012-02-08 8:36 ` Daniel Hartwig
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=CAN3veRfSY29+zHLXNmfky+1qxoztF-MZgGRdgh_PDBF06qGbiw@mail.gmail.com \
--to=mandyke@gmail.com \
--cc=guile-devel@gnu.org \
/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).