From: "Ludovic Courtès" <ludo@gnu.org>
To: 無無 <yuvallangerontheroad@gmail.com>
Cc: 67760-done@debbugs.gnu.org
Subject: bug#67760: Add the guile-srfi-232 package for curried procedures
Date: Fri, 05 Jan 2024 17:25:34 +0100 [thread overview]
Message-ID: <87v887eoht.fsf@gnu.org> (raw)
In-Reply-To: <CABKQn8GEaLgM83sZ1e1GrE=LuqsXLpKw9DO+ctsAKqQyhDg8Bg@mail.gmail.com> ("無無"'s message of "Mon, 11 Dec 2023 03:14:40 +0200")
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hi,
無無 <yuvallangerontheroad@gmail.com> skribis:
> From c88c0502b2036c7a33fcb9c402de69eb14634831 Mon Sep 17 00:00:00 2001
> Message-Id: <c88c0502b2036c7a33fcb9c402de69eb14634831.1702256938.git.yuval.langer@gmail.com>
> From: Yuval Langer <yuval.langer@gmail.com>
> Date: Mon, 11 Dec 2023 03:00:50 +0200
> Subject: [PATCH] Add the guile-srfi-232 package for curried procedures.
>
> ---
> gnu/packages/guile-xyz.scm | 51 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
Applied with the changes below, thanks!
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1806 bytes --]
diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm
index 6df9fc851f..75e3754046 100644
--- a/gnu/packages/guile-xyz.scm
+++ b/gnu/packages/guile-xyz.scm
@@ -3858,8 +3858,7 @@ (define-public guile-srfi-232
(arguments
(list
#:phases
- #~(modify-phases
- %standard-phases
+ #~(modify-phases %standard-phases
(add-after 'unpack 'move-and-delete-things
(lambda _
(let* ((srfi-directory (string-append #$output "/srfi")))
@@ -3881,14 +3880,14 @@ (define-public guile-srfi-232
(home-page "https://github.com/scheme-requests-for-implementation/srfi-232")
(synopsis "Flexible curried procedures")
(description
- "Scheme lacks a flexible way to create and apply curried
-procedures. This SRFI describes curried, a variant of lambda that
-creates true curried procedures which also behave just like ordinary
-Scheme procedures. They can be applied to their arguments one by one,
-all at once, or anywhere in between, without any novel syntax.
-curried also supports nullary and variadic procedures, and procedures
-created with it have predictable behavior when applied to surplus
-arguments.")
+ " This package provides an implementation of
+@uref{https://srfi.schemers.org/srfi-232/srfi-232.html, SRFI-232}, which
+describes @code{curried}, a variant of @code{lambda} that creates true curried
+procedures which also behave just like ordinary Scheme procedures. They can
+be applied to their arguments one by one, all at once, or anywhere in between,
+without any novel syntax. @code{curried} also supports nullary and variadic
+procedures, and procedures created with it have predictable behavior when
+applied to surplus arguments.")
(license license:expat)))
(define-public emacsy
prev parent reply other threads:[~2024-01-05 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 1:14 [bug#67760] Add the guile-srfi-232 package for curried procedures 無無
2024-01-05 16:25 ` 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=87v887eoht.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=67760-done@debbugs.gnu.org \
--cc=yuvallangerontheroad@gmail.com \
/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).