From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH 1/2] srfi-34: Replace the 'raise' core binding.
Date: Fri, 29 Nov 2019 12:00:44 +0100 [thread overview]
Message-ID: <87imn3c5gj.fsf@igalia.com> (raw)
In-Reply-To: <87y2w26axz.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 26 Nov 2019 14:09:44 +0100")
On Tue 26 Nov 2019 14:09, Ludovic Courtès <ludo@gnu.org> writes:
> AFAICS there are two blockers:
>
> 1. We cannot replace & re-export at the same time.
Following discussion on IRC, this is fixed now, with
#:re-export-and-replace. Would be nice if #:re-export could know
whether a binding is local or re-exported and DTRT but that isn't the
case currently.
> 2. ‘raise’ takes exactly one argument, whereas ‘raise-exception’ takes
> an additional keyword argument.
I think ignoring this one is fine FWIW.
> Perhaps also we should provide a mechanism similar to GCC attributes to
> mark a procedure as throwing, so that the compiler can DTRT?
An interesting option :) FWIW the compiler has to also know how to call
the callee... Something to think about.
Cheers,
Andy
next prev parent reply other threads:[~2019-11-29 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 16:45 [PATCH 0/2] Silence run-time warnings for SRFI-3[45] Ludovic Courtès
2019-11-25 16:45 ` [PATCH 1/2] srfi-34: Replace the 'raise' core binding Ludovic Courtès
2019-11-26 10:09 ` Andy Wingo
2019-11-26 13:09 ` Ludovic Courtès
2019-11-29 11:00 ` Andy Wingo [this message]
2019-11-25 16:45 ` [PATCH 2/2] srfi-35: Replace '&error' Ludovic Courtès
2019-11-26 10:10 ` Andy Wingo
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=87imn3c5gj.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guile-devel@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.
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).