From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Stefan Israelsson Tampe" <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Fwd: [Patch] definitions in when, unless, do as well as in cond- and case-clauses
Date: Mon, 07 Feb 2022 06:56:37 +0100 [thread overview]
Message-ID: <8b364eb9-ac93-4166-8564-bd4c48274af1@www.fastmail.com> (raw)
In-Reply-To: <CAGua6m37+ZBydSRpPrGZqwK_xoLrpsD9Tf1mch=6SbKcc3c20w@mail.gmail.com>
Historical garage maybe. I just remember some old bug in WebKit where let was a lot slower than var because it created what was called lexical context which affected interpreter speed because of some kind of linear time variable lookup.
Anyway, that stuff doesn't apply to guile versions after 2. Especially since a (let () body ...) where the body contains no (define ...) gets converted to a (begin body ...) by the optimizer.
The behaviour of begin Vs let is well specified and any begin outside of a body context is just chain of expressions. It just lacks internal definitions.
--
Linus Björnstam
On Sun, 6 Feb 2022, at 21:13, Stefan Israelsson Tampe wrote:
> Hmm just why conditionals use begin and not let,
>
> On Sun, Feb 6, 2022 at 11:49 AM <tomas@tuxteam.de> wrote:
>> On Sun, Feb 06, 2022 at 10:45:54AM +0100, Linus Björnstam wrote:
>> > You need to use ,optimize.
>>
>> Thanks you both, Maxime and Linus, for giving me a new lantern :)
>>
>> Cheers
>> --
>> t
prev parent reply other threads:[~2022-02-07 5:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 19:11 [Patch] definitions in when, unless, do as well as in cond- and case-clauses Linus Björnstam
2021-06-17 9:06 ` Maxime Devos
2021-06-17 12:57 ` Linus Björnstam
2021-06-17 13:54 ` Maxime Devos
2022-02-03 10:48 ` Linus Björnstam
[not found] ` <CAGua6m1Cqe=aLOD7-jfzoqxP1aOxvWn3=UgcKyk+Dx7_51Bq3w@mail.gmail.com>
2022-02-04 20:11 ` Fwd: " Stefan Israelsson Tampe
2022-02-04 20:58 ` Maxime Devos
[not found] ` <CAGua6m11r27x=rq4S4fF09vHY+S-Az7GOZfmoT41hEBDSkLJQg@mail.gmail.com>
2022-02-04 21:40 ` Fwd: " Stefan Israelsson Tampe
2022-02-04 23:39 ` Maxime Devos
2022-02-05 1:14 ` Stefan Israelsson Tampe
2022-02-05 10:55 ` Maxime Devos
2022-02-05 17:31 ` Stefan Israelsson Tampe
2022-02-05 17:36 ` Maxime Devos
2022-02-06 6:44 ` Linus Björnstam
2022-02-06 9:27 ` tomas
2022-02-06 9:40 ` Maxime Devos
2022-02-06 9:45 ` Linus Björnstam
2022-02-06 10:48 ` tomas
2022-02-06 20:13 ` Stefan Israelsson Tampe
2022-02-06 20:28 ` Maxime Devos
2022-02-06 20:31 ` tomas
[not found] ` <CAGua6m3BHMXOhT3PHZcxdqHqHomTFESO31j5CcSNK3pbA7K-Kg@mail.gmail.com>
2022-02-06 21:26 ` Maxime Devos
2022-02-06 21:27 ` Maxime Devos
2022-02-07 5:56 ` Linus Björnstam [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://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=8b364eb9-ac93-4166-8564-bd4c48274af1@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@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.
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).