From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Cc: "Mark H. Weaver" <mhw@netris.org>
Subject: Re: upcoming patches
Date: Tue, 27 Oct 2009 21:15:08 +0100 [thread overview]
Message-ID: <m3iqe0lhkj.fsf@pobox.com> (raw)
In-Reply-To: <m3skdhc7h7.fsf@pobox.com> (Andy Wingo's message of "Sun, 18 Oct 2009 12:38:28 +0200")
Hey,
On Sun 18 Oct 2009 12:38, Andy Wingo <wingo@pobox.com> writes:
> My todo list, for the record:
>
> 1) Finish case-lambda branch -- should be a day or two's work there
>
> This doesn't necessarily imply that all the new features
> (case-lambda, lambda*, ...) are fully baked, but the VM, debugging,
> and IL support for the features should be mergeable and documented.
Well, that ended up being 3 or 4 days' work, but all the features are
there and documented.
> 2) Make sure Mark's patch is in
I'm going to do it! I will! :)
Mark, I realized that we can have (hashv '()) == (hashv #f). In a hashv
table the hashv selects the bucket, but within the bucket elements are
compared with eqv? -- and (eqv? '() #f) => #f. So I don't see any
problems there.
> 3) Merge Daniel's work
This is next!
> Then I will finish GOOPS dispatch in Scheme with case-lambda and
> predicates, and then see if I can merge in subr-simplification,
> getting all dispatch into the VM.
I hope to get this all in before the next release. We'll see!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-10-27 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 10:38 upcoming patches Andy Wingo
2009-10-18 21:43 ` Neil Jerram
2009-10-19 18:24 ` Andy Wingo
2009-10-19 21:08 ` Neil Jerram
2009-10-19 21:17 ` Andy Wingo
2009-10-20 16:47 ` Mark H Weaver
2009-10-20 19:19 ` Andy Wingo
2009-10-19 12:34 ` Daniel Kraft
2009-10-19 18:26 ` Andy Wingo
2009-10-27 20:15 ` Andy Wingo [this message]
2009-10-27 21:17 ` Neil Jerram
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=m3iqe0lhkj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).