From: zimoun <zimon.toutoune@gmail.com>
To: "Magali Lemes" <magalilemes00@gmail.com>,
"Gábor Boskovits" <boskovits@gmail.com>,
guix-devel@gnu.org
Subject: Re: [Outreachy] Use of impure functional programming and use of vlists
Date: Fri, 05 Mar 2021 01:06:48 +0100 [thread overview]
Message-ID: <86zgzi79bb.fsf@gmail.com> (raw)
In-Reply-To: <b20f3d5b-f4bb-a204-f430-7bcdfb5c5f1c@gmail.com>
Hi Magali,
On Sat, 27 Feb 2021 at 00:10, Magali Lemes <magalilemes00@gmail.com> wrote:
> As my Outreachy internship approaches an end, I'd like to know which of
> the following options is better for walking and displaying the Git
> commit history:
> 1) having a list and then using for-each it to display the commit
> information;
> 2) display the list while building it.
What could be informative is to benchmark the two cases. For an
example, see my previous tests on your code:
<https://yhetil.org/guix/86eei4hamb.fsf@gmail.com>
Profiling the 2 functions should be also helpful. Feel free to ask on
guix-devel how to profile with Guile.
Cheers,
simon
prev parent reply other threads:[~2021-03-05 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 3:10 [Outreachy] Use of impure functional programming and use of vlists Magali Lemes
2021-02-27 12:36 ` Arun Isaac
2021-03-03 14:00 ` Ludovic Courtès
2021-03-05 0:06 ` zimoun [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zgzi79bb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=magalilemes00@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).