From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: CPS thoughts
Date: Mon, 20 May 2013 23:21:10 -0400 [thread overview]
Message-ID: <CA+U71=P--wXFG4sn0hiWggRgYPH6z4Od7qXxvMphaktTjvMkNA@mail.gmail.com> (raw)
In-Reply-To: <87ppwl9zgi.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Hello,
Thanks for the review.
On Mon, May 20, 2013 at 4:19 PM, Andy Wingo <wingo@pobox.com> wrote:
> Some first thoughts on the CPS language, just after having looked at
> (language cps):
>
> * Overall looking really good.
>
Thanks! You may choose to retract that after you see the other files, of
course. :-)
> * License blocks are missing.
>
> * Toplevel comments should be prefixed by ";;; " (three semicolons).
>
> * Overview could go in the module commentary section.
>
These three should be simple to fix.
> * Missing distinction between original names and unique names.
>
Yes, I agree. I think it even reuses original names sometimes, which is not
good. I should just rename everything.
> * Missing source information.
>
The issue here is not that it's hard to pass source information through to
the compiler, but that I haven't figured out what to do with it when I have
it. I imagine that your ELF work has solved this problem.
> * Missing procedure properties.
>
Can you explain what you mean? Does the compiler need to handle procedure
properties specially?
> * Why is there no "let" that can bind functions? You don't always want
> to set up a recursive binding environment.
>
> * Lambdas are missing lambda* and case-lambda support.
>
With these two, it's just that I haven't implemented it yet. I'll try to do
it quickly, although I don't know how much time I'll have to work on it.
> What do you think about rebasing? wip-rtl-may-2013 is a good target
> until wip-rtl goes into master.
>
Sounds great! I think the compiler stuff is fairly separate from the RTL
stuff - when I've rebased it occasionally, it hasn't been a problem.
Best,
Noah
[-- Attachment #2: Type: text/html, Size: 3098 bytes --]
next prev parent reply other threads:[~2013-05-21 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 20:19 CPS thoughts Andy Wingo
2013-05-21 3:21 ` Noah Lavine [this message]
2013-05-21 19:46 ` Andy Wingo
2013-05-22 4:33 ` Noah Lavine
2013-05-23 4:05 ` Noah Lavine
2013-05-23 7:20 ` 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='CA+U71=P--wXFG4sn0hiWggRgYPH6z4Od7qXxvMphaktTjvMkNA@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).