From: Attila Lendvai <attila@lendvai.name>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
52600@debbugs.gnu.org,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Andrew Tropin" <andrew@trop.in>
Subject: [bug#52600] [PATCH] doc: Document (gnu services configuration).
Date: Tue, 18 Jan 2022 09:24:13 +0000 [thread overview]
Message-ID: <WKogm98_O511PtLC8RGROQidOqEQRgUmpLt8NXJwHMVldiQdI5Yqr5tK0uGVvQj1y_tHzEcL7xdDl3IGnNdFGpaFXao8zY9fTUXtxYSSuiM=@lendvai.name> (raw)
In-Reply-To: <87a6grcwh7.fsf@yoctocell.xyz>
> I am not familiar with Guile internals, but I think that
> ‘#<unspecified>’ is just a thing that the pretty-printer prints. Maybe
> we could use “proper” Maybe types, like in SRFI-189[1]?
>
> [1]: Using https://srfi.schemers.org/srfi-189/srfi-189.html
this is indeed a good idea here, thanks for drawing my attention to
it! FTR, i have added guile-srfi-189 in this (not yet applied)
patch:
https://issues.guix.gnu.org/53317
i think Maybe and Nothing covers exactly what i need here. my plan is
to get guile-srfi-189 into master, then make sure it can be used in
the Guix codebase, and then prepare a patch for the configuration code
that uses Nothing to represent unspecified values.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
Government means never having to say you're sorry…
next prev parent reply other threads:[~2022-01-18 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 15:12 [bug#52600] [PATCH] doc: Document (gnu services configuration) Xinglu Chen
2021-12-22 22:14 ` Ludovic Courtès
2021-12-23 10:42 ` Xinglu Chen
[not found] ` <IxmgfjO9lp2ladC6D9lHKww0c_r1R0JsnoPJbKD9vg1StRq5QIaZyf3If6Jc16dYnqBdbM0VAjy2PDpZBWxwhHHvgJj_lL8sE4SJ8AsG3po=@lendvai.name>
2021-12-23 12:54 ` Xinglu Chen
2021-12-23 15:21 ` Attila Lendvai
2022-01-18 9:24 ` Attila Lendvai [this message]
2022-01-06 14:20 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='WKogm98_O511PtLC8RGROQidOqEQRgUmpLt8NXJwHMVldiQdI5Yqr5tK0uGVvQj1y_tHzEcL7xdDl3IGnNdFGpaFXao8zY9fTUXtxYSSuiM=@lendvai.name' \
--to=attila@lendvai.name \
--cc=52600@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=public@yoctocell.xyz \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).