From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: using an SRFI that is not available in Guile
Date: Tue, 18 Jan 2022 17:06:28 +0000 [thread overview]
Message-ID: <SdytAhEJA2w1yf10t0j6doraN8YIbONJ4Y3FCznPJC-PINBfz45n2oRB_mAOza4qVrMYUXOEZj-x_-mH6GIj4nIu95_ri_2eEHdBZyeN_e4=@lendvai.name> (raw)
In-Reply-To: <87iluhf5ci.fsf@gnu.org>
> There’s no widespread “Maybe” idiom in Scheme; or rather, people use
> TYPE | #f as a way to approximate “Maybe”. It’s not ideal, primarily
> because appropriate handling is not statically checked. Yet, that’s
> what we have and I’m not convinced adding SRFI-189 to the mix would
> bring enough of an improvement to justify it.
>
> Thoughts?
configurations are full of boolean fields, where #f is a valid value.
to represent unset fields, we would essentially need to implement half
of srfi-189 (Maybe and Nothing), and in a potentially buggy way
(e.g. using a symbol like 'disabled to represent an unset field value
(i.e. the current solution) clashes with a field type of symbol?).
i don't think it's worth rolling our own when an srfi covers what we
need.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Go find yourself first, so you can find me.”
— Rumi (1207–1273)
next prev parent reply other threads:[~2022-01-18 17:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:46 using an SRFI that is not available in Guile Attila Lendvai
2022-01-12 17:01 ` Attila Lendvai
2022-01-12 17:09 ` Maxime Devos
2022-01-13 9:55 ` Attila Lendvai
2022-01-13 10:49 ` Maxime Devos
2022-01-13 18:20 ` Attila Lendvai
2022-01-13 20:48 ` Attila Lendvai
2022-01-14 12:02 ` Maxime Devos
2022-01-17 13:45 ` Attila Lendvai
2022-01-13 10:53 ` Maxime Devos
2022-01-13 10:56 ` Maxime Devos
2022-01-18 15:09 ` Ludovic Courtès
2022-01-18 17:06 ` Attila Lendvai [this message]
2022-01-19 10:34 ` Ludovic Courtès
2022-01-21 13:59 ` Attila Lendvai
2022-01-24 15:41 ` Ludovic Courtès
2022-01-24 23:02 ` Attila Lendvai
2022-02-05 11:13 ` Ludovic Courtès
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='SdytAhEJA2w1yf10t0j6doraN8YIbONJ4Y3FCznPJC-PINBfz45n2oRB_mAOza4qVrMYUXOEZj-x_-mH6GIj4nIu95_ri_2eEHdBZyeN_e4=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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.