From: adriano <randomlooser@riseup.net>
To: Vijay Marupudi <vijaymarupudi@gatech.edu>,
guile-user <guile-user@gnu.org>
Subject: Re: code review request
Date: Sun, 27 Feb 2022 11:51:52 +0100 [thread overview]
Message-ID: <1071fe5c8b31e3d5c77b5519ff05aa8df205a915.camel@riseup.net> (raw)
In-Reply-To: <87y21xlh4l.fsf@vijaymarupudi.com>
Il giorno sab, 26/02/2022 alle 11.36 -0500, Vijay Marupudi ha scritto:
> > I get a result I don't understand: this return 2 values
>
> Reading the source code, the second value is an implementation
> detail,
> keeping track of the visited directories.
>
> > One is expected, it's the one I wanted to produce
>
> Great! I would ignore the second value, because it is a by product of
> the recursive implementation of file-system-fold, where it passes the
> visited list to recursive invocations of itself.
>
> ~ Vijay
Thank you
The manual says:
" Files and directories, as identified by their device/inode number
pair, are traversed only once. "
I assumed this meant this was kept track of internally, I didn't expect
this to be part of what the procedure returns
Thanks again
prev parent reply other threads:[~2022-02-27 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 10:31 code review request adriano
2022-02-26 16:36 ` Vijay Marupudi
2022-02-27 10:51 ` adriano [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=1071fe5c8b31e3d5c77b5519ff05aa8df205a915.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guile-user@gnu.org \
--cc=vijaymarupudi@gatech.edu \
/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).