unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 59390-done@debbugs.gnu.org
Subject: bug#59390: [PATCH 0/5] Doing 'match-record' work at expansion time
Date: Fri, 02 Dec 2022 00:07:42 +0100	[thread overview]
Message-ID: <87wn7awwn5.fsf@gnu.org> (raw)
In-Reply-To: <20221119222326.10644-1-ludo@gnu.org> ("Ludovic Courtès"'s message of "Sat, 19 Nov 2022 23:23:26 +0100")

Ludovic Courtès <ludo@gnu.org> skribis:

> This addresses a longstanding issue: making ‘match-record’ efficient,
> and allowing it to error out on unknown field names at macro-expansion
> time.

I went ahead, rebased, and pushed these:

  00ddf185e6 services: networking: Avoid 'match' on records.
  adfe1064c8 services: base: Use 'match-record' instead of 'match'.
  4c8eea027a home: services: Use 'match-record' instead of 'match'.
  cc9ee514e3 doc: Recommend 'match-record'.
  7c1161dba4 records: 'match-record' checks fields at macro-expansion time.

This change breaks the ABI: we’ll have to run:

  make clean-go && make

Inquiries welcome!

Ludo’.




      parent reply	other threads:[~2022-12-01 23:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 22:23 [bug#59390] [PATCH 0/5] Doing 'match-record' work at expansion time Ludovic Courtès
2022-11-19 22:24 ` [bug#59390] [PATCH 1/5] records: 'match-record' checks fields at macro-expansion time Ludovic Courtès
2022-11-19 22:24   ` [bug#59390] [PATCH 2/5] doc: Recommend 'match-record' Ludovic Courtès
2022-11-19 22:24   ` [bug#59390] [PATCH 3/5] home: services: Use 'match-record' instead of 'match' Ludovic Courtès
2022-11-19 22:24   ` [bug#59390] [PATCH 4/5] services: base: " Ludovic Courtès
2022-11-19 22:24   ` [bug#59390] [PATCH 5/5] services: networking: Avoid 'match' on records Ludovic Courtès
2022-12-01 23:07 ` 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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wn7awwn5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=59390-done@debbugs.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 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).