From: Xinglu Chen <public@yoctocell.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48867@debbugs.gnu.org
Subject: [bug#48867] [PATCH] gnu: Add guile-define.
Date: Wed, 09 Jun 2021 13:15:42 +0200 [thread overview]
Message-ID: <87bl8fqof5.fsf@yoctocell.xyz> (raw)
In-Reply-To: <875yyodp4j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Tue, Jun 08 2021, Ludovic Courtès wrote:
> Hi,
>
> Xinglu Chen <public@yoctocell.xyz> skribis:
>
>> * gnu/packages/guile-xyz.scm (guile-define): New variable.
>
> [...]
>
>> + (native-inputs
>> + `(("guile" ,guile-3.0)))
>> + (home-page "https://hg.sr.ht/~bjoli/guile-define")
>> + (synopsis "Definitions in expression contexts for Guile")
>> + (description "This package provides a utility macro to allow
>> +@code{define}s in expression contexts of function bodies.")
>
> This may have been useful with Guile 2.x but it’s useless with 3.0,
> which already allows that:
>
> --8<---------------cut here---------------start------------->8---
> scheme@(guile-user)> (version)
> $9 = "3.0.7"
> scheme@(guile-user)> (define (divide-minus-one a b)
> (when (= b 1) (error "We don't allow that here"))
> (define b* (- b 1))
> (/ a b*))
> scheme@(guile-user)>
> --8<---------------cut here---------------end--------------->8---
>
> So either we make the package depend on 2.x, or we drop it. Dropping it
> is probably the best option if there are no dependents.
>
> Thoughts?
Oh, I didn’t know that, then I think it’s fine to drop the package.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2021-06-09 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 9:55 [bug#48867] [PATCH] gnu: Add guile-define Xinglu Chen
2021-06-08 21:26 ` Ludovic Courtès
2021-06-09 11:15 ` Xinglu Chen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl8fqof5.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=48867@debbugs.gnu.org \
--cc=ludo@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.