From: Walter Lewis <wklew@mailbox.org>
To: Jean Abou Samra <jean@abou-samra.fr>,
guile-user@gnu.org, arne_bab@web.de
Subject: Re: Breaking hygiene with syntax-rules?
Date: Fri, 11 Aug 2023 20:19:08 -0400 [thread overview]
Message-ID: <e2e74674-7a2d-543d-16e9-27707bff2f90@mailbox.org> (raw)
In-Reply-To: <f4ee2a64a983f07455f03c99adfdc2e9ffa5fb00.camel@abou-samra.fr>
Hi Jean,
> You could just turn that into a syntax-case macro, use gensym to
> generate the names, and insert them using with-syntax or quasisyntax.
Yes, this is what I ended up doing before I saw your other reply.
> By the way, I'm rather confused as to why you deem this caching
> useful. A priori, I would expect a simple bytevector->pointer call
> would be just as fast as a to-pointer call. Do you somehow create lots
> of pointers to the contents of the same bytevector so that weak
> references they hold incur a noticeable GC overhead?
To be honest I don't know enough about C to know the performance of
bytevector->pointer, so I was assuming Chickadee's approach was done for
a reason. But if you think it's not a big deal then I'm happy to
simplify things! I think I will remove this caching for now.
Thanks for your help, and Arne as well for digging into the issue.
Best,
Walter
next prev parent reply other threads:[~2023-08-12 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 2:35 Breaking hygiene with syntax-rules? Walter Lewis via General Guile related discussions
2023-08-11 5:07 ` Dr. Arne Babenhauserheide
2023-08-11 8:00 ` Jean Abou Samra
2023-08-11 8:33 ` Dr. Arne Babenhauserheide
2023-08-11 23:57 ` Jean Abou Samra
2023-08-12 5:57 ` Dr. Arne Babenhauserheide
2023-08-11 13:34 ` Walter Lewis via General Guile related discussions
2023-08-11 22:50 ` Walter Lewis via General Guile related discussions
2023-08-11 23:55 ` Jean Abou Samra
2023-08-11 23:57 ` Jean Abou Samra
2023-08-12 0:19 ` Walter Lewis [this message]
2023-08-12 0:58 ` Jean Abou Samra
2023-08-12 5:59 ` Dr. Arne Babenhauserheide
2023-08-14 19:26 ` Thompson, David
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=e2e74674-7a2d-543d-16e9-27707bff2f90@mailbox.org \
--to=wklew@mailbox.org \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=jean@abou-samra.fr \
/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).