From: Brian Cully via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Αντώνιος Τσώλης" <tsolis.antonios@gmail.com>, 62698@debbugs.gnu.org
Subject: bug#62698: bind:utils
Date: Wed, 03 May 2023 12:58:33 -0400 [thread overview]
Message-ID: <87mt2lpcr9.fsf@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <87fs8dzhzl.fsf@gmail.com>
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Thanks for finding the problem. Should we leave this bug open
> until
> specification->package+output is properly documented in our
> manual, with
> an example? If yes, would you like to try your hand at adding
> it?
I've looked at this briefly, and can't figure out a good place to
document this (I'm also not particularly good with TexInfo).
I'm okay with closing the bug. Though I will say that I think this
procedure is a bit of a foot-gun. Multiple value returns are
always kind of weird, and in this particular case I don't see the
value at all; the only reason to use
‘specification->package+output’ would be to get both the package
and the output, so the minor advantages of multi-value returns are
obviated. On top of that, does this even get used outside of
system/home definitions? And in those places you always want a
list.
I realize a lot of code uses the current semantics, so changing
them would be extremely difficult at this late stage. It's worth
thinking about adding another procedure that does the expected
thing (returning a list of package and output), IMHO, and
transitioning over to that.
-bjc
next prev parent reply other threads:[~2023-05-03 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 11:43 bug#62698: bind:utils Αντώνιος Τσώλης
2023-04-06 18:27 ` Brian Cully via Bug reports for GNU Guix
2023-04-06 20:03 ` Αντώνιος Τσώλης
2023-04-07 22:25 ` Brian Cully via Bug reports for GNU Guix
2023-04-08 5:43 ` Αντώνιος Τσώλης
2023-04-08 15:12 ` Brian Cully via Bug reports for GNU Guix
2023-05-03 13:01 ` Maxim Cournoyer
2023-05-03 16:58 ` Brian Cully via Bug reports for GNU Guix [this message]
2023-05-04 12:43 ` Maxim Cournoyer
2023-04-07 13:26 ` Jonathan Brielmaier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt2lpcr9.fsf@psyduck.jhoto.kublai.com \
--to=bug-guix@gnu.org \
--cc=62698@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=maxim.cournoyer@gmail.com \
--cc=tsolis.antonios@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.