From: Tomas Volf <~@wolfsden.cz>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 68305@debbugs.gnu.org
Subject: [bug#68305] [PATCH] gnu: Add guile-srfi-197.
Date: Fri, 12 Jan 2024 17:47:16 +0100 [thread overview]
Message-ID: <ZaFtFHFTwS3Z4Y-K@ws> (raw)
In-Reply-To: <87mstar0qd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On 2024-01-12 17:10:50 +0100, Mathieu Othacehe wrote:
>
> Hello,
>
> > +(define-public guile-srfi-197
> > + (let ((commit "d31b8be86460bf837cccf2737a1b9b9c01788573")
> > + (revision "0"))
>
> You should explain why you are not using a release with a comment. The
> "final" tag for instance.
Comment added.
>
> > + #~(modify-phases %standard-phases
> > + (add-after 'unpack 'create-module
> > + (λ _
>
> Please use 'lambda'.
I replaced all occurrences. Is there something regarding this in the manual? I
see no mention of it and guix style leaves it as it is. There are few (~5) uses
in the repository already, so I assumed it is permitted.
>
> > +SRFI defines a family of chain and nest pipeline operators, which can rewrite
> > +nested expressions like (a b (c d (e f g))) as a sequence of operations:
>
> @code{(a b (c d (e f g)))}
>
> > +(chain g (e f _) (c d _) (a b _)).")
>
> @code{(chain g (e f _) (c d _) (a b _)).")}
>
> Can you please send a v2?
Done and done.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-12 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 15:09 [bug#68305] [PATCH] gnu: Add guile-srfi-197 Tomas Volf
2024-01-12 16:10 ` Mathieu Othacehe
2024-01-12 16:47 ` Tomas Volf [this message]
2024-01-13 9:22 ` Mathieu Othacehe
2024-01-12 16:46 ` [bug#68305] [PATCH v2] " Tomas Volf
2024-01-13 9:40 ` bug#68305: " Mathieu Othacehe
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=ZaFtFHFTwS3Z4Y-K@ws \
--to=~@wolfsden.cz \
--cc=68305@debbugs.gnu.org \
--cc=othacehe@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).