Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "David Allsopp" <dra-news@metastack.com>
To: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] Re: Hash clash in polymorphic variants
Date: Mon, 14 Jan 2008 15:37:50 -0000	[thread overview]
Message-ID: <001401c856c3$6c692260$6c7ba8c0@countertenor> (raw)
In-Reply-To: <200801140956.25449.ober.14@osu.edu>

Kuba Ober wrote:
> On Monday 14 January 2008, Stefan Monnier wrote:
> > > What I meant was simply that instead of using some fixed hash
> > > function, one could use a perfect hashing function which is optimal
> > > for its known set of inputs, and won't ever generate a collision.
> >
> > The problem is that the set of inputs is not know at compile time, only
> > at link time.
>
> As I've said in the cited post, the perfect hash generator would have to
> be invoked at link time, which shouldn't be a big deal.

Assuming you're talking hypothetically and designing a new runtime then,
yes, it's not a big deal.

However, this scheme could not just be dropped into the present system - it
would not work with dynamic linking because once you've hashed a polymorphic
variant tag-name you drop the name so you can't re-hash when you update your
perfect hashing function... unless you can devise a perfect hashing scheme
that hashes all the old keys to their old values and new ones to
non-clashing new values ;o)

Internally, `Foo is indistinguishable from the int 3505894* - so if
caml_hash_variant("Foo") suddenly changes value mid-program then any
previous instances of `Foo in memory cease to be equal to it!


David


* Try:
# (Obj.magic `Foo : int);;
- : int = 3505894
# (Obj.magic 3505894) = `Foo;;
- : bool = true

I don't know whether caml_hash_variant varies between version or even
platform so the actual number may be different on other systems.


  reply	other threads:[~2008-01-14 15:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 17:09 Jon Harrop
2008-01-10 20:35 ` [Caml-list] " Eric Cooper
2008-01-10 21:24   ` Jon Harrop
2008-01-10 21:40     ` David Allsopp
2008-01-11 13:30       ` Kuba Ober
2008-01-11 13:48         ` Jon Harrop
2008-01-11 16:14           ` Kuba Ober
2008-01-11 18:40             ` David Allsopp
2008-01-14 12:20               ` Kuba Ober
2008-01-14 14:44                 ` Stefan Monnier
2008-01-14 14:56                   ` [Caml-list] " Kuba Ober
2008-01-14 15:37                     ` David Allsopp [this message]
2008-01-14 15:44                       ` Kuba Ober
2008-01-14 16:03                         ` David Allsopp
2008-01-14 15:45                     ` Stefan Monnier
2008-01-15  3:36                     ` [Caml-list] " Jacques Garrigue
2008-01-15  4:59                       ` Jon Harrop
2008-01-15  9:01                         ` Jacques Garrigue
2008-01-15 18:17                           ` Jon Harrop
2008-01-15 19:20                             ` Gerd Stolpmann
2008-01-15 22:04                               ` Jon Harrop
2008-01-16 13:48                                 ` Kuba Ober
2008-01-16 15:02                                   ` Dario Teixeira
2008-01-16 19:00                                     ` Jon Harrop
2008-01-17 13:09                                     ` Kuba Ober
2008-01-18  5:33                                 ` Kuba Ober
2008-01-18  5:19                               ` Kuba Ober
2008-01-18  5:39                                 ` Kuba Ober
2008-01-16  3:26                             ` Jacques GARRIGUE
2008-01-16  3:34                               ` Yaron Minsky
2008-01-16  3:42                                 ` Jon Harrop
2008-01-16  4:40                               ` Jon Harrop
2008-01-16 16:03                                 ` Eric Cooper
2008-01-16 10:50                             ` Richard Jones
2008-01-14 17:14                   ` Jon Harrop
2008-01-14 17:36                     ` Alain Frisch
2008-01-11  0:15 ` [Caml-list] " Jacques Garrigue

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='001401c856c3$6c692260$6c7ba8c0@countertenor' \
    --to=dra-news@metastack.com \
    --cc=caml-list@yquem.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