From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: My Guile 2.0.8 TODO list
Date: Wed, 06 Mar 2013 15:08:47 +0100 [thread overview]
Message-ID: <87ip54d3io.fsf@gnu.org> (raw)
In-Reply-To: 87vc95czw8.fsf@tines.lan
Mark H Weaver <mhw@netris.org> skribis:
> FYI, here's what I'm hoping to get into Guile 2.0.8.
Thanks for sharing.
> * #!optional and #!rest reader handling.
As a reader option, right?
> * Add command-line option to augment %load-compiled-path.
+1
> * [Ludovic?] Fix par-map and par-for-each to not overflow the stack for
> large lists.
Yes, I’ll look into it. I’ll also look at other bugs I reported over
the weeks.
Ludo’.
next prev parent reply other threads:[~2013-03-06 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 21:14 My Guile 2.0.8 TODO list Mark H Weaver
2013-03-06 14:08 ` Ludovic Courtès [this message]
2013-03-06 18:45 ` Andrew Gaylard
2013-03-08 9:33 ` 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=87ip54d3io.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).