From: "CUOQ Pascal" <Pascal.CUOQ@cea.fr>
To: "Matthias Puech" <puech@cs.unibo.it>
Cc: <caml-list@yquem.inria.fr>
Subject: Re: Sets and home-made ordered types
Date: Thu, 17 Sep 2009 11:07:56 +0200 [thread overview]
Message-ID: <5EFD4D7AC6265F4D9D3A849CEA9219191AB20E@LAXA.intra.cea.fr> (raw)
In-Reply-To: <4AB1F740.9020404@cs.unibo.it>
> So what, one pointer more for each association
> in the Map? That would be rather acceptable (but still not ideal, sorry
> I'm very demanding).
You were already paying the price of "one pointer more"
many times over and were not even thinking about it. One
more will not make any difference.
You have to realize that each node already carries a height,
two pointers to subtrees, and take into account the one-word
overhead for the block header. We're not doubling the size of
each tree node here, we're increasing it from 5 to 6 words.
Pascal
PS: You make up for the overhead by having dynamic structures
that are just the right size, and by taking advantage of sharing,
of course.
next prev parent reply other threads:[~2009-09-17 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090917030607.927BCBCA9@yquem.inria.fr>
2009-09-17 6:21 ` Caml-list] " CUOQ Pascal
2009-09-17 8:45 ` [Caml-list] " Matthias Puech
2009-09-17 9:07 ` CUOQ Pascal [this message]
2009-09-16 16:40 Matthias Puech
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=5EFD4D7AC6265F4D9D3A849CEA9219191AB20E@LAXA.intra.cea.fr \
--to=pascal.cuoq@cea.fr \
--cc=caml-list@yquem.inria.fr \
--cc=puech@cs.unibo.it \
/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).