From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: antlers <antlers@illucid.net>, guix-devel@gnu.org
Subject: Re: A friendlier API for operating-system declarations
Date: Mon, 26 Feb 2024 20:58:22 +0100 [thread overview]
Message-ID: <b274b18b9bbed99b7b3ced8240955c0bf3ff1a22.camel@gmail.com> (raw)
In-Reply-To: <4c6c7b82-08e2-45e6-b0e9-e4b9f5d155d6@app.fastmail.com>
Am Sonntag, dem 25.02.2024 um 13:27 -0800 schrieb antlers:
> Thanks for the detailed response c:
>
> The blocker is that AFAIK we can't tell if a record-field was defined
> as thunk-ed or delay-ed outside of the expansion of the
> `define-record-type*' form that defines it, nor programatically
> access it's getter/setter (the pair `(guix records)` defines, which
> accounts for eg. thunk-ing, and is distinct from the underlying pair
> returned by eg. `record-accessor').
You might want to have a look at match-record or even define your
modify-record in terms of it. IIUC it ought to handle exactly the
problem you're talking about while also making it slightly easier for
you to structure your updating code.
Cheers
next prev parent reply other threads:[~2024-02-26 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 22:25 A friendlier API for operating-system declarations antlers
[not found] ` <87plwrj3w9.fsf@rdklein.fr>
2024-02-20 3:42 ` antlers
2024-02-25 9:26 ` Liliana Marie Prikler
2024-02-25 18:49 ` antlers
2024-02-25 20:47 ` antlers
2024-02-25 20:50 ` Liliana Marie Prikler
2024-02-25 21:27 ` antlers
2024-02-26 19:58 ` Liliana Marie Prikler [this message]
2024-03-01 16:44 ` Hartmut Goebel
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 3:31 antlers
2023-03-23 8:06 Edouard Klein
2023-03-23 18:48 ` Josselin Poiret
2023-03-23 20:23 ` Edouard Klein
2023-03-23 21:05 ` Liliana Marie Prikler
2023-04-13 9:42 ` Ludovic Courtès
2023-05-18 14:37 ` Edouard Klein
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=b274b18b9bbed99b7b3ced8240955c0bf3ff1a22.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=antlers@illucid.net \
--cc=guix-devel@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.