Thank you for your encouragement!

I am currently talking to Matthew Flatt about getting the change
upstream. If this happens before SRFI 260 is finalised, we may just
have to include a link to Chez Scheme.

A patch file in the SRFI repo would soon only apply only to a very
dated version of Chez Scheme, so I wonder whether this would be of
much help.

Am Fr., 31. Jan. 2025 um 17:15 Uhr schrieb Arthur A. Gleckler
<xxxxxx@speechcode.com>:
>
> On Fri, Jan 31, 2025 at 2:49 AM Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>>
>> I implemented generated symbols natively in Chez Scheme. The native
>> implementation generates the unique names lazily.
>
>
> Excellent.  We should include this as a supplement to the sample implementation.  We could include a link to the diff in your repo, but that would require keeping your repo up indefinitely.  We could include a patch file in the SRFI repo instead.  If your change is upstreamed, we could then point to the Chez implementation.
>
> What do you think?
>
> On Fri, Jan 31, 2025 at 2:49 AM Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>>
>> I implemented generated symbols natively in Chez Scheme. The native
>> implementation generates the unique names lazily.
>>
>> You can find the patched Chez Scheme here:
>>
>> https://github.com/mnieper/ChezScheme/tree/srfi-260
>>
>> The procedure `generate-symbol` is exported by the `(chezscheme)`
>> library (also known as `(scheme)`).
>>
>> Marc