From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Pippijn van Steenhoven <pip88nl@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Clarification for the configuration of comparison functions
Date: Wed, 10 Sep 2014 14:51:39 +0200 [thread overview]
Message-ID: <1410353499.3003.29.camel@thinkpad> (raw)
In-Reply-To: <20140910124101.GA30231@xinutec.org>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
Am Mittwoch, den 10.09.2014, 13:41 +0100 schrieb Pippijn van Steenhoven:
> On Wed, Sep 10, 2014 at 02:26:28PM +0200, Gerd Stolpmann wrote:
> > type t = ...
> > type t_cmp = t * int
> >
> > let wrap x = (x, Hashtbl.hash x)
> >
> > let my_compare (x1,h1) (x2,h2) =
> > if h1=h2 then
> > compare x1 x2
> > else
> > h1-h2
>
> This code is incorrect when h1 is large and negative.
Hashtbl.hash returns non-negative ints. For other hash functions you are
correct.
> You should use
> "compare h1 h2" and annotate h1 and/or h2 with its type (int), so that
> int-compare is called directly.
>
> Also, if you store the hash before the actual value, compare will
> probably stop comparing after it finds that the hashes are not equal, so
> you can simply use the polymorphic compare on t_cmp. I don't know this
> for sure, since I haven't looked at the source, but I would assume this
> is true.
The OCaml manual doesn't define compare for tuples, so you cannot
exploit that. I wouldn't bet that compare runs from left to right over
the values, as OCaml is known for sometimes preferring right to left.
But maybe this could be a future language feature? If the OCaml manual
defined compare on tuples, this would in deed be a fine trick.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-10 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 8:56 SF Markus Elfring
2014-09-10 11:27 ` Gerd Stolpmann
2014-09-10 12:07 ` Yotam Barnoy
2014-09-10 12:26 ` Gerd Stolpmann
2014-09-10 12:37 ` Adrien Nader
2014-09-10 12:38 ` Yotam Barnoy
2014-09-10 12:41 ` Pippijn van Steenhoven
2014-09-10 12:51 ` Gerd Stolpmann [this message]
2014-09-10 12:56 ` Ben Millwood
[not found] ` <CAADdkeKquMWyHjQhgd2SOZYr9DaS2E+i3Ug5=xb25BK-+n16eQ@mail.gmail.com>
2014-09-10 12:44 ` Gerd Stolpmann
2014-09-10 20:56 ` SF Markus Elfring
2014-09-11 7:46 ` Francois Berenger
2014-09-11 8:10 ` SF Markus Elfring
2014-09-11 8:24 ` Francois Berenger
2014-09-11 8:33 ` SF Markus Elfring
2014-09-11 8:39 ` Frédéric Bour
2014-10-06 20:50 ` SF Markus Elfring
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=1410353499.3003.29.camel@thinkpad \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=pip88nl@gmail.com \
/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