GNU bug report logs - #56799
(gnu services configuration) usage of *unspecified* is problematic

Previous Next

Full log

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 56799 <at> debbugs.gnu.org, attila <at> lendvai.name, bug-guix <at> gnu.org
Subject: Re: bug#56799: (gnu services configuration) usage of *unspecified*
 is problematic
Date: Wed, 27 Jul 2022 18:43:25 +0200

[Message part 1 (text/plain, inline)]

Hi Maxim,

Maxim Cournoyer 写道：
> I'd suggest we revisit 8cb1a49a3998c39f315a4199b7d4a121a6d66449 
> to use
> 'unspecified (the symbol) instead of *unspecified*, which *can* 
> be
> serialized without any fuss in gexps.

Bah.  Could we provide our own reader?

I'd much rather this be addressed in Guile (or failing that, 
transparently by Guix) than have to deal with some magical symbol. 
IIRC that was the argument for using *unspecified* in the first 
place, and I think it makes sense.

This looks more like an unexplored oversight than a well-reasoned 
restriction to me.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.