From: Andy Wingo <wingo@pobox.com>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: 24357@debbugs.gnu.org
Subject: bug#24357: pure guile program leaks memory
Date: Sat, 03 Sep 2016 11:54:58 +0200 [thread overview]
Message-ID: <87d1kli9zh.fsf@pobox.com> (raw)
In-Reply-To: <891b344e747119b497e1d0a17b62b81b@hypermove.net> (Amirouche Boubekki's message of "Sat, 03 Sep 2016 09:20:36 +0200")
On Sat 03 Sep 2016 09:20, Amirouche Boubekki <amirouche@hypermove.net> writes:
> Using guile 2.1.3, I have a program that:
>
> - reads urls from a text file
> - download the urls using curl command via popen
> - output the result to stdout
>
> Also, it relies on n-for-each-par-map for ice-9 threads.
Can you reduce it please? For example, remove the use of threads.
Andy
next prev parent reply other threads:[~2016-09-03 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 7:20 bug#24357: pure guile program leaks memory Amirouche Boubekki
2016-09-03 9:54 ` Andy Wingo [this message]
2016-09-03 18:49 ` Amirouche Boubekki
2016-09-12 17:47 ` Amirouche Boubekki
2017-03-01 9:06 ` Andy Wingo
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=87d1kli9zh.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=24357@debbugs.gnu.org \
--cc=amirouche@hypermove.net \
/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).