[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56799: (gnu services configuration) usage of *unspecified* is proble
From: |
Maxim Cournoyer |
Subject: |
bug#56799: (gnu services configuration) usage of *unspecified* is problematic |
Date: |
Thu, 28 Jul 2022 11:09:46 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
Hi Maxime,
Maxime Devos <maximedevos@telenet.be> writes:
[...]
> I think it would be better to:
>
> * gradually move away from *unspecified* to (values)
> * and this way, gradually change the meaning of *unspecified* from "an
> unspecified value" to 'an atom you can do with as you want"
> * after this, unspecified? and making #<unspecified> readable by the
> reader aren't weird anymore
Or perhaps simply introduce a #none or other special syntax similar to
None in Python, that would serve a different purpose that *unspecified*,
and be orthogonal to it. It seems that'd be less confusing and simpler.
Thanks,
Maxim
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, (continued)
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, Tobias Geerinckx-Rice, 2022/07/27
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, Maxim Cournoyer, 2022/07/27
- bug#56799: [PATCH] services: configuration: Step back from *unspecified*., Maxim Cournoyer, 2022/07/27
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, Maxim Cournoyer, 2022/07/27
- bug#56799: [PATCH v2] gexp: Handle *unspecified* as a gexp input., Maxim Cournoyer, 2022/07/27
- bug#56799: [PATCH v2] gexp: Handle *unspecified* as a gexp input., Maxime Devos, 2022/07/27
- bug#56799: [PATCH v2] gexp: Handle *unspecified* as a gexp input., Maxim Cournoyer, 2022/07/28
- bug#56799: [PATCH v3] gexp: Handle *unspecified* as a gexp input., Maxim Cournoyer, 2022/07/28
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, bokr, 2022/07/28
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic, Maxime Devos, 2022/07/28
- bug#56799: (gnu services configuration) usage of *unspecified* is problematic,
Maxim Cournoyer <=