From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Maxime Devos <maximedevos@telenet.be>, 56114@debbugs.gnu.org
Subject: bug#56114: Guix does not have a documented general and practical procedure for lowering a single lowerable object to the /gnu/store/... string.
Date: Tue, 05 Jul 2022 09:57:19 +0200 [thread overview]
Message-ID: <87wncs56w0.fsf@gnu.org> (raw)
In-Reply-To: <865ykczgh7.fsf@gmail.com> (zimoun's message of "Mon, 04 Jul 2022 23:59:48 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> My comment was about an unrelated thing.
I don’t take comments about unrelated things. ;-)
> Well, I do not use every day G-exp nor ’plain-file’ and the like. The
> interface appears to me unexpected each time I use it but hey I can
> live with it. :-) However, the documentation (or docstring) does not
> appear clear, each time I have my «aaah right!» moment.
[...]
> it is hard to guess beforehand that ’plain-file’ and ’mixed-text-file’
> do not return the same type of file-like object.
As someone who writes gexps and manipulates “file-like objects”, it
doesn’t matter whether a thing lowers to a derivation or to a plain
store item. What matters is that you can insert it in a gexp and it’ll
do the right thing. That’s why the docstrings don’t insist on that
difference.
Hope it makes sense!
Ludo’.
next prev parent reply other threads:[~2022-07-05 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 21:01 bug#56114: Guix does not have a documented general and practical procedure for lowering a single lowerable object to the /gnu/store/... string Maxime Devos
2022-07-03 20:50 ` Ludovic Courtès
2022-07-04 15:43 ` zimoun
2022-07-04 20:13 ` Ludovic Courtès
2022-07-04 21:59 ` zimoun
2022-07-05 7:57 ` Ludovic Courtès [this message]
2022-07-05 10:13 ` zimoun
2022-07-10 20:03 ` Joshua Branson via Bug reports for GNU Guix
2022-07-15 15:41 ` Ludovic Courtès
2022-07-19 14:10 ` Maxime Devos
2022-07-07 22:25 ` jbranso--- via Bug reports for GNU Guix
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=87wncs56w0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56114@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--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).