From: Attila Lendvai <attila@lendvai.name>
To: "53663-close@debbugs.gnu.org" <53663-close@debbugs.gnu.org>
Subject: bug#53663: Fw: Re: bug#53663: [PATCH] gnu: services: Also accept 'undefined in maybe-foo? constructs.
Date: Wed, 02 Feb 2022 11:47:02 +0000 [thread overview]
Message-ID: <LZAnSJmgmdtLPRzpDhrfzSlilVJJq1MLXCWIIkE-yMLDeEXnFN5wPrWeMGAjZGo2vl1yUKPrilT3nCtusH9frolHVuqEM9boV1MLWgVr64U=@lendvai.name> (raw)
In-Reply-To: <Go3Xae9pfXgOvYZqOORu5yBtXDUCzhtCzs2XryuL9XDL_MZGi3wYlo9wRcGvm_daPJPmPbx3nEx566pf22YVGJVN9mmBL_Iu8NRwdBQN7Ec=@lendvai.name>
> What would be different here?
the possibility of writing:
(define-configuration my-cfg
(my-field (maybe-string)))
versus now having to write:
(define-configuration my-cfg
(my-field (maybe-string 'disabled)))
but now that i thought about it, i think everyone is better off if i
deal with this on my side, instead of having a discussion about the
exact shape of a bandaid.
closing this for now; more later in the form of a proper cleanup
proposal of the configuration code.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“There can be no greater stretch of arbitrary power than is required to seize children from their parents, teach them whatever the authorities decree they shall be taught, and expropriate from the parents the funds to pay for the procedure.”
— Isabel Paterson (1886–1961), 'The God of the Machine' (1943)
prev parent reply other threads:[~2022-02-02 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:27 [bug#53663] [PATCH] gnu: services: Also accept 'undefined in maybe-foo? constructs Attila Lendvai
2022-02-01 9:53 ` Ludovic Courtès
[not found] ` <Go3Xae9pfXgOvYZqOORu5yBtXDUCzhtCzs2XryuL9XDL_MZGi3wYlo9wRcGvm_daPJPmPbx3nEx566pf22YVGJVN9mmBL_Iu8NRwdBQN7Ec=@lendvai.name>
2022-02-02 11:47 ` Attila Lendvai [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='LZAnSJmgmdtLPRzpDhrfzSlilVJJq1MLXCWIIkE-yMLDeEXnFN5wPrWeMGAjZGo2vl1yUKPrilT3nCtusH9frolHVuqEM9boV1MLWgVr64U=@lendvai.name' \
--to=attila@lendvai.name \
--cc=53663-close@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.