-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expansion of templates with leading ellipsis - do not allow invalid templates #1013
Comments
The point is the template pattern is
is simply invalid. I should probably update it to throw an exception in that case. |
Ah, I misread the standard. Only the improper tail is a "subtemplate". Sorry! |
Wait... If a single element should be after the ellipsis, then it only makes sense to use Let me see if I understand this right: in page 24 of R7RS,
Then,
So there could be several templates, in sequence, and any of them could be of the form And since Is my interpretation correct? |
It's an escaping mechanism. So the most trivial case is indeed |
Sorry, I misunderstood what you had said. Right, I re-read R7RS, and see where my misinterpretation was. |
Hello!
From what I understand of R7RS, the templates beginning with ellipses, like
(... a b c etc)
are expressed as a list, but not expanded as one (that is, they should be spliced into the code generated from the template).That the text says "
(<ellipsis> <template>)
is identical to<template>
" seems to indicate that the list should be spliced (no?)Also,
seems to be concordant with that.
For example:
would splice the
(c ... d)
list into the expanded form:But Chibi seems to not splice the list:
unless it's a single ellipsis (?)
Maybe I didn't get some detail (sorry for the noise if this is the case).
The text was updated successfully, but these errors were encountered: