From: "Ludovic Courtès" <ludo@gnu.org>
To: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
Cc: lloda <lloda@sarc.name>, <guile-devel@gnu.org>,
Andy Wingo <wingo@pobox.com>
Subject: Re: Add internal definitions to derived forms
Date: Wed, 25 Jan 2023 16:09:48 +0100 [thread overview]
Message-ID: <87y1pqslab.fsf@gnu.org> (raw)
In-Reply-To: <2f38c5ea-0cb6-494e-b680-70b39c3291fb@app.fastmail.com> ("Linus Björnstam"'s message of "Wed, 09 Nov 2022 16:32:29 +0100")
Hello!
Linus Björnstam <linus.bjornstam@veryfast.biz> skribis:
> This commit adds internal definitions to derived conditional forms,
> with-fluids and and-let*. This means the bodies of when, unless and
> with-fluids, and the clause bodies of case and cond behave like a
> lambda body.
>
> There is no performance hit since guile optimizes a (let () ...)
> without internal definitions to a begin (i.e: no new lexical context
> is created).
Daniel pushed this as 764e3614b8c13de604399572a67d071621e9ca21 in
‘main’. I had completely overlooked this thread but I wasn’t quite sure
about it, so I did not include it in 3.0.9.
The reason I’m hesitant is that, while I think it’s nice to be able to
have local ‘define’ in these contexts, I’m wary of diverging from R5RS
and R6RS. Since it’s a one-way change (we won’t be able to revert it
once people rely on it), I thought we’d rather be careful.
What do people think? Andy?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-01-25 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 15:32 Add internal definitions to derived forms Linus Björnstam
2022-11-09 15:46 ` Damien Mattei
2022-11-17 7:25 ` lloda
2022-11-18 9:04 ` Linus Björnstam
2022-11-18 9:27 ` Lassi Kortela
2022-11-18 9:50 ` Linus Björnstam
2022-11-18 10:22 ` Lassi Kortela
2022-11-18 12:53 ` Linus Björnstam
2022-11-18 13:18 ` Lassi Kortela
2023-01-19 17:54 ` lloda
2023-01-20 17:37 ` lloda
2023-01-23 22:13 ` Ludovic Courtès
2023-01-23 23:28 ` lloda
2023-01-24 7:33 ` Linus Björnstam
2023-01-24 9:02 ` Ludovic Courtès
2023-01-24 17:59 ` lloda
2023-01-25 10:33 ` Ludovic Courtès
2023-01-25 15:09 ` Ludovic Courtès [this message]
2023-01-25 15:38 ` Greg Troxel
2023-01-25 21:38 ` Linus Björnstam
2023-01-25 21:06 ` Linus Björnstam
2023-02-02 11:17 ` lloda
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1pqslab.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=linus.bjornstam@veryfast.biz \
--cc=lloda@sarc.name \
--cc=wingo@pobox.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.
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).