all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bruno Victal <mirai@makinata.eu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Relocating some procedures into (guix utils)
Date: Sat, 25 Feb 2023 18:37:52 +0100	[thread overview]
Message-ID: <87wn45y7bj.fsf@gnu.org> (raw)
In-Reply-To: <f940bfb5-794e-39dc-8d93-8e99ccbca478@makinata.eu> (Bruno Victal's message of "Sat, 21 Jan 2023 00:14:53 +0000")

Hi,

Bruno Victal <mirai@makinata.eu> skribis:

> IMO there are some procedures (or even modules) that could be relocated into (guix utils) as their utility is more general than what their module names would suggest.
>
> Good candidates to relocate into (guix utils):
> * (gnu home services utils)

Hmm, not sure.

> * list-of, interpose, alist?, list-of-string? from (gnu services configuration)

I think it’s fine to keep them over there.  :-)

The rationale is that one Shouldn’t™ be using things like ‘alist?’ and
‘list-of-string?’ in “real code”: they have linear complexity (like
‘list?’), they might be ill-defined, and we don’t generally write
polymorphic code anyway.

They *are* useful though as a limited form of contracts for
‘define-configuration’ fields, so it’s good to keep them there.

Taking a step back, my inclination is to keep things local, or even
private, until/unless there’s clear evidence of (1) usefulness beyond
their initial place of birth, and (2) the interface is “clean” enough
for them to be promoted.  #2 is subjective, so it’s really on a
case-by-case basis.

My 2¢!

Ludo’.


      reply	other threads:[~2023-02-25 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  0:14 Relocating some procedures into (guix utils) Bruno Victal
2023-02-25 17:37 ` Ludovic Courtès [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=87wn45y7bj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mirai@makinata.eu \
    /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.