[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we find a better idiom for unversioned packages?
From: |
Taylan Kammer |
Subject: |
Re: Can we find a better idiom for unversioned packages? |
Date: |
Sat, 4 Sep 2021 14:32:48 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
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
Re: Can we find a better idiom for unversioned packages?, Leo Famulari, 2021/09/02
Re: Can we find a better idiom for unversioned packages?, Sarah Morgensen, 2021/09/03
Re: Can we find a better idiom for unversioned packages?, Sarah Morgensen, 2021/09/03
Re: Can we find a better idiom for unversioned packages?, Ludovic Courtès, 2021/09/08