caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Aleksey Nogin <nogin@cs.caltech.edu>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Pervasives.compare output type
Date: Thu, 31 Mar 2005 21:59:32 -0800	[thread overview]
Message-ID: <424CE344.20409@cs.caltech.edu> (raw)
In-Reply-To: <4243DD0D.1060100@barettadeit.com>

On 25.03.2005 01:42, Alex Baretta wrote:

>>> let f1  x       y = Pervasives.compare x y
>>> let f2 (x: int) y = Pervasives.compare x y
>>> let f3  x       y = if x=y then Pervasives.compare "s1" "s2" else if 
>>> x < y then -1 else 1
>>> let f4 (x: int) y = if x=y then Pervasives.compare "s1" "s2" else if 
>>> x < y then -1 else 1
>>> let f5  x       y = let i = Pervasives.compare x y in if i = 0 then 
>>> Pervasives.compare "s1" "s2" else i
>>> let f6 (x: int) y = let i = Pervasives.compare x y in if i = 0 then 
>>> Pervasives.compare "s1" "s2" else i
>>> let f7  x       y = match Pervasives.compare x y with 0 -> 
>>> Pervasives.compare "s1" "s2" | i -> i
>>> let f8 (x: int) y = match Pervasives.compare x y with 0 -> 
>>> Pervasives.compare "s1" "s2" | i -> i
>>>
>>> let time name f =
>>>   
> 
> 
> I am unsure as to how to interpret these benchmarks...

Yes, these were taken a bit out of context. Basically, the question we 
were discussing was:
> What's the fastest way to compare int*string pairs (or, in general - int*'a), where ints are likely to be distinct whenever the second elements are distinct (basically, the int is a hash)?


The answer is that the "f4" above is the fastest one:

let compair_pair ((i1:int), a1) (i2, a2) =
    if i1 = i2 then
       Pervasives.compare a1 a2
    else if i1 < i2 then
       -1
    else
       1

-- 
Aleksey Nogin

Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200


  reply	other threads:[~2005-04-01  5:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 18:47 Alex Baretta
2005-03-24 19:41 ` [Caml-list] " Richard Jones
2005-03-24 21:00   ` Marcin 'Qrczak' Kowalczyk
2005-03-24 21:38     ` Bardur Arantsson
2005-03-24 22:07       ` [Caml-list] " Jason Hickey
2005-03-24 22:26         ` brogoff
2005-03-25  9:42         ` Alex Baretta
2005-04-01  5:59           ` Aleksey Nogin [this message]
2005-03-24 22:15       ` Marcin 'Qrczak' Kowalczyk
2005-03-24 22:41         ` Bardur Arantsson
2005-03-25  9:43         ` [Caml-list] " Alex Baretta
2005-03-29  7:14 ` [Caml-list] " Oliver Bandel
2005-03-30 14:17 ` Xavier Leroy
2005-03-30 14:45   ` Alex Baretta
2005-03-30 15:11     ` Jacques Carette
2005-03-30 15:28       ` Alex Baretta
2005-03-30 17:47       ` brogoff
2005-03-30 18:21         ` Jacques Carette
2005-03-30 18:49           ` brogoff
2005-03-30 20:06             ` Jon Harrop
2005-03-30 20:43               ` Jacques Carette
2005-03-30 22:14                 ` Christopher Dutchyn
2005-03-31  0:44                 ` brogoff
2005-03-30 22:43             ` GADT?? (Re: [Caml-list] Pervasives.compare output type) Oliver Bandel
2005-03-30 22:35     ` [Caml-list] Pervasives.compare output type Oliver Bandel

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=424CE344.20409@cs.caltech.edu \
    --to=nogin@cs.caltech.edu \
    --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).