From: Andy Wingo <wingo@igalia.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: 48098-done@debbugs.gnu.org
Subject: bug#48098: let/ec compilation bug
Date: Sun, 02 May 2021 15:43:41 +0200 [thread overview]
Message-ID: <87r1ipjlo2.fsf@igalia.com> (raw)
In-Reply-To: <CAGua6m3642LYw7dR1uz2+ACWeB8y4DCjLdh0-r+9bep3w_y6Ww@mail.gmail.com> (Stefan Israelsson Tampe's message of "Thu, 29 Apr 2021 12:48:55 +0200")
Thanks for the report; fixed!
On Thu 29 Apr 2021 12:48, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> Here is an interesting test case that shows that fi we define
> (define-syntax-rule (letec-m f) (let/ec c (f c)))
> (define (letec-f f) (let/ec c (f c)))
>
> we can get two different behaviors with letec-m compiles wrongly. Obviously a bug!
>
> This is important in casy you would like to make a loop macro effectively with a continue directive.
prev parent reply other threads:[~2021-05-02 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:48 bug#48098: let/ec compilation bug Stefan Israelsson Tampe
2021-05-02 13:43 ` Andy Wingo [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=87r1ipjlo2.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=48098-done@debbugs.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).