From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org
Subject: Re: Guix records
Date: Fri, 26 Feb 2021 18:36:17 +0100 [thread overview]
Message-ID: <87zgzqwx2m.fsf@gnu.org> (raw)
In-Reply-To: 87lfc2e9vn.fsf@clara
Hi,
Olivier Dion via General Guile related discussions <guile-user@gnu.org>
skribis:
> In the module (guix records), there's some very nice syntax rule
> `define-record-type*` that allows very powerfull declarative style of
> records. For example:
> ----------------------------------------------------------------------
> (employee
> (age 30)
> (name "Foo")
> (profession "Teacher"))
> ----------------------------------------------------------------------
>
> I would like to use this feature in my software. However, I don't want
> to have Guix as a dependency only for that. For now, I've copied the
> content of (guix records) into (my-software records). But this put
> burden of maitenance into my hands.
I think it’s a reasonable maintenance burden though, since it’s fairly
independent, it rarely changes, and you can always copy updated versions
from Guix when you want to.
That said, I agree it’s not ideal, and we should look towards making it
a standalone library. I’m a bit reluctant to doing that just yet
because it’s convenient in Guix to be able to adjust it when we need it.
Thanks,
Ludo’.
prev parent reply other threads:[~2021-02-26 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 16:51 Guix records Olivier Dion via General Guile related discussions
2021-02-09 23:14 ` Taylan Kammer
2021-02-10 1:02 ` Dr. Arne Babenhauserheide
2021-02-10 5:37 ` Taylan Kammer
2021-02-10 8:38 ` Dr. Arne Babenhauserheide
2021-02-09 23:32 ` Aleix Conchillo Flaqué
2021-02-10 0:28 ` Olivier Dion via General Guile related discussions
2021-02-10 21:11 ` Aleix Conchillo Flaqué
2021-02-26 17:36 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgzqwx2m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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.
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).