summaryrefslogtreecommitdiff
path: root/gnu/services/configuration.scm
diff options
context:
space:
mode:
authorAttila Lendvai <attila@lendvai.name>2022-08-24 14:40:42 +0200
committerMaxim Cournoyer <maxim.cournoyer@gmail.com>2022-08-25 00:10:42 -0400
commit6fb9759ef3b8eb2a2b10c3f02a57ece29b5c53ba (patch)
treed595379184b9aae3617ccffcc07bc08abb35de3f /gnu/services/configuration.scm
parentee08277a70d29b6d707524a4e17620f50b87adf4 (diff)
services: configuration: Change the value of the unset marker.
The new value of %unset-value sticks out more when something goes wrong, and is also more unique; i.e. easier to search for. Signed-off-by: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Diffstat (limited to 'gnu/services/configuration.scm')
-rw-r--r--gnu/services/configuration.scm5
1 files changed, 3 insertions, 2 deletions
diff --git a/gnu/services/configuration.scm b/gnu/services/configuration.scm
index 60965486a7..83da63c1b3 100644
--- a/gnu/services/configuration.scm
+++ b/gnu/services/configuration.scm
@@ -305,12 +305,13 @@ does not have a default value" field kind)))
;; Ideally this should be an implementation detail, but we export it
;; to provide a simpler API that enables unsetting a configuration
-;; field that has a maybe type, but also a default value.
+;; field that has a maybe type, but also a default value. We give it
+;; a value that sticks out to the reader when something goes wrong.
;;
;; An example use-case would be something like a network application
;; that uses a default port, but the field can explicitly be unset to
;; request a random port at startup.
-(define %unset-value 'unset)
+(define %unset-value '%unset-marker%)
(define (maybe-value-set? value)
"Predicate to check whether a 'maybe' value was explicitly provided."