unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Appending Queues
Date: Fri, 02 Nov 2012 23:11:29 +0100	[thread overview]
Message-ID: <87r4obmz8u.fsf@gnu.org> (raw)
In-Reply-To: 87boff3org.fsf@googlemail.com

Hi,

Ian Price <ianprice90@googlemail.com> skribis:

> Noah Lavine <noah.b.lavine@gmail.com> writes:
>
>> The only change I was considering is allowing an arbitrary number of
>> arguments, but that's something I can implement if people agree that
>> we want the functions in (ice-9 q).
>
> I'm loath to add anything to (ice-9 q) since I find the names, and
> the lack of a distinct type, less than satisfactory.

+1.  And there are functional queue implementations around that are
worth promoting, IMO.

Ian: would you like to turn (pfds queues) into a patch against Guile?
:-)

Thanks,
Ludo’.




      parent reply	other threads:[~2012-11-02 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 19:59 Appending Queues Noah Lavine
2012-11-02 17:20 ` Ian Price
2012-11-02 18:00   ` Noah Lavine
2012-11-02 22:11   ` Ludovic Courtès [this message]

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=87r4obmz8u.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).