unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Taylan Kammer <taylan.kammer@gmail.com>
To: Liliana Marie Prikler <leo.prikler@student.tugraz.at>,
	Sarah Morgensen <iskarian@mgsn.dev>
Cc: guix-devel@gnu.org, Xinglu Chen <public@yoctocell.xyz>
Subject: Re: Can we find a better idiom for unversioned packages?
Date: Sat, 4 Sep 2021 14:32:48 +0200	[thread overview]
Message-ID: <0a357d78-ec1a-faba-cfb1-a1b916631e70@gmail.com> (raw)
In-Reply-To: <a02776967a9850fc276d5ffc1da3708929e1a075.camel@student.tugraz.at>

On 04.09.2021 00:11, Liliana Marie Prikler wrote:
>
> Well, let #f or *unspecified* would also solve the git blame issue, [...]
> 

Only partially on-topic but: I believe *unspecified* should not be used
explicitly in code.  It's an implementation detail, and by avoiding it in
user code, we lessen the burden on the Guile maintainers to stick to this
particular implementation detail for backwards compatibility.

I'd advise #f or (values) for a "no meaningful return value" situation.

-- 
Taylan


  reply	other threads:[~2021-09-04 12:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 21:14 Can we find a better idiom for unversioned packages? Sarah Morgensen
2021-09-03 22:11 ` Liliana Marie Prikler
2021-09-04 12:32   ` Taylan Kammer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-03  5:51 Sarah Morgensen
2021-08-31 19:57 Sarah Morgensen
2021-08-31 21:20 ` Maxime Devos
2021-09-01 12:11   ` Xinglu Chen
2021-09-01 16:29     ` Maxime Devos
2021-09-01 13:33   ` Liliana Marie Prikler
2021-09-01 16:39     ` Maxime Devos
2021-09-01 18:34       ` Liliana Marie Prikler
2021-09-02 14:09         ` Maxime Devos
2021-09-02 14:20           ` Liliana Marie Prikler
2021-09-02 14:34             ` Maxime Devos
2021-09-01 19:48       ` Jonathan McHugh
2021-09-01 21:47         ` Liliana Marie Prikler
2021-09-02 13:32           ` Maxime Devos
2021-09-02  7:53         ` Jonathan McHugh
2021-09-02  9:25           ` Liliana Marie Prikler
2021-09-01 10:55 ` Xinglu Chen
2021-09-01 15:37   ` Leo Famulari
2021-09-01 16:50     ` Xinglu Chen
2021-09-02 16:51       ` Leo Famulari
2021-09-02 17:29         ` Leo Famulari
2021-09-03 16:11           ` Xinglu Chen
2021-09-03 16:35             ` Leo Famulari
2021-09-03 16:57               ` Leo Famulari
2021-09-03 20:03               ` Xinglu Chen
2021-09-04 21:00                 ` Leo Famulari
2021-09-08 21:15       ` Ludovic Courtès
2021-09-02 17:08 ` Leo Famulari
2021-09-08 21:28 ` Ludovic Courtès
2021-09-08 22:21 ` Jonathan McHugh
2021-09-08 22:38   ` Leo Famulari

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=0a357d78-ec1a-faba-cfb1-a1b916631e70@gmail.com \
    --to=taylan.kammer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=iskarian@mgsn.dev \
    --cc=leo.prikler@student.tugraz.at \
    --cc=public@yoctocell.xyz \
    /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).