From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: guile-devel@gnu.org
Subject: define-inlinable* : a define-inlinable with lambda*-behaviour.
Date: Fri, 24 Apr 2020 09:13:22 +0200 [thread overview]
Message-ID: <e47df4d4-47ea-409a-b77f-748476c10ca1@www.fastmail.com> (raw)
I just found that (ice-9 optargs) has defmacro*, which made me think about a question that has popped up on irc about once every 4 months: why isn't there a define-inlinable*?
I have a working implementation, and I want to know if there is any interest to include it in guile. Either in boot-9.scm, or as a friend of defmacro* in (ice-9 opt-args).
A straight forward simple implementation would have a regression over define-inlinable: define-inlinable does arg count validation, which is a lot less simple when you have keywords and/or optional arguments. Would this be an acceptable regression if they are implemented as two distinct macros?
If one does a proper define-inlinable*, it can be used to implement define-inlinable (since that would be the simple case for it).
What do the maintainers think?
--
Linus Björnstam
reply other threads:[~2020-04-24 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e47df4d4-47ea-409a-b77f-748476c10ca1@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=guile-devel@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).