unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Magali Lemes <magalilemes00@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>,
	zimoun <zimon.toutoune@gmail.com>,
	guix-devel@gnu.org
Subject: [Outreachy] Use of impure functional programming and use of vlists
Date: Sat, 27 Feb 2021 00:10:05 -0300	[thread overview]
Message-ID: <b20f3d5b-f4bb-a204-f430-7bcdfb5c5f1c@gmail.com> (raw)

Hello, Guix.

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.

When it comes to option number 2, the main advantage is that it's faster 
to perform operations such as 'guix git log --oneline | head -n5'. The 
downside is that it's not a pure functional programming approach.
Another question is, could vlists be used? Since it would be fast to 
have the commits in a hash table implemented with vlists, we could use 
'vlist-for-each' to display the commits. I haven't seen vlist-for-each 
being used anywhere in Guix, so I wondered if there's a special reason 
for it not being used, or if it hasn't really been necessary at all thus 
far.

Regards,
Magali



             reply	other threads:[~2021-02-27  3:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27  3:10 Magali Lemes [this message]
2021-02-27 12:36 ` [Outreachy] Use of impure functional programming and use of vlists Arun Isaac
2021-03-03 14:00 ` Ludovic Courtès
2021-03-05  0:06 ` zimoun

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=b20f3d5b-f4bb-a204-f430-7bcdfb5c5f1c@gmail.com \
    --to=magalilemes00@gmail.com \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@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).