From: "Benjamin C. Pierce" <bcpierce@saul.cis.upenn.edu>
To: Chet Murthy <chet@watson.ibm.com>
Cc: Greg Morrisett <jgm@cs.cornell.edu>, caml-list@inria.fr
Subject: Re: de Bruijn indices
Date: Thu, 12 Oct 2000 14:08:56 EDT [thread overview]
Message-ID: <22679.971374136@saul.cis.upenn.edu> (raw)
In-Reply-To: Your message of Thu, 12 Oct 2000 10:57:56 -0400. <200010121457.KAA04527@nautilus-chet.watson.ibm.com>
> Now, there _is_ possibly one way of doing explicit names that would be
> fast enough to be a contender -- where the names are chosen uniquely,
> using a global counter, so no capture check is required. I can
> imagine that that would be fast.
This is pretty much how the Pict front end works. We started out with a
standard deBruijn representation, but later switched to a scheme where,
during parsing, we choose a globally unique spelling for each bound name
(they're not *that* ugly). We have to do a little work later to make
sure that uniqueness is maintained, but it seems faster on the whole.
B
next prev parent reply other threads:[~2000-10-13 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 18:09 Greg Morrisett
2000-10-12 14:57 ` Chet Murthy
2000-10-12 18:08 ` Benjamin C. Pierce [this message]
2000-10-12 18:19 ` Trevor Jim
-- strict thread matches above, loose matches on Subject: below --
2000-10-12 19:09 John R Harrison
2000-10-12 17:33 Greg Morrisett
2000-10-11 11:26 Simon Peyton-Jones
2000-10-11 20:12 ` Markus Mottl
2000-10-10 18:30 John R Harrison
2000-10-09 7:19 de Bruijn indices (Re: WWW Page of Team PLClub) Eijiro Sumii
2000-10-10 14:04 ` de Bruijn indices Gerard Huet
2000-10-10 17:29 ` Chet Murthy
2000-10-11 22:35 ` John Max Skaller
2000-10-05 23:29 Patrick M Doane
2000-10-06 8:15 ` Markus Mottl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22679.971374136@saul.cis.upenn.edu \
--to=bcpierce@saul.cis.upenn.edu \
--cc=bcpierce@cis.upenn.edu \
--cc=caml-list@inria.fr \
--cc=chet@watson.ibm.com \
--cc=jgm@cs.cornell.edu \
/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