From: Sebastien Carlier <sebc@posse42.net>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Cc: Alex Baretta <alex@baretta.com>
Subject: Re: [Caml-list] "Nasty" functions and memory usage
Date: Mon, 19 Mar 2001 17:01:48 +0100 [thread overview]
Message-ID: <20010319170148.A5637@posse42.net> (raw)
In-Reply-To: <3AB624F9.5B6C6680@baretta.com>; from alex@baretta.com on Mon, Mar 19, 2001 at 04:25:45PM +0100
Alex Baretta wrote:
> Now, my question is, how come the memory usage of the Ocaml (3.00)
> front end does not grow with time as it attempts to compute the
> type of, say, f6?
I think it's pretty-printing that is actually taking a lot of time.
During inference you would only have (2**n) types because there is a
lot of sharing. However, if you try to print the type you will really
have (2**(2**n)) nodes to traverse.
--
Sebastien
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-03-19 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-17 1:35 Alex Baretta
[not found] ` <E14exRm-0001kT-00@ithif51>
2001-03-19 15:25 ` Alex Baretta
2001-03-19 16:01 ` Sebastien Carlier [this message]
2001-03-22 14:22 ` Xavier Leroy
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=20010319170148.A5637@posse42.net \
--to=sebc@posse42.net \
--cc=alex@baretta.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).