caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: forum@x9c.fr
To: caml-list@inria.fr
Cc: forum@x9c.fr
Subject: Re: [Caml-list] [ANN] Argot: 1.0 release
Date: Fri, 04 Nov 2011 13:45:47 +0100	[thread overview]
Message-ID: <20111104134547.14475ul9wx5myyrk@ssl0.ovh.net> (raw)
In-Reply-To: <CALgo1QJfveoXsmnyHOeVhyA+DWHPOFf=_9yvPEvbFOptePLfqw@mail.gmail.com>

Daniel Bünzli <daniel.buenzli@erratique.ch> a écrit :

(...)


>> The searching tools are quite limited currently,
>
> To me the search tools are not so useful. Usually I know in which
> module I want to lookup a function. To get there quickly I use my OS
> file search --- thanks to ocamldoc generating one file per module ---
> and then the incremental search of my browser. Of course this is quite
> different of indexing e.g. the symbols directly but it works well in
> practice.

Well, regarding search by name, I consider that the only advantages upon
browser search are:
   - simultaneous search on several pages;
   - regular expression search (although some browser may support it).


(...)

> Regarding search by type, I wonder if people actually use this for
> useful reasons or if it's just out of curiosity or for the cool hack
> factor -- and sure it's cool. I mean there's not enough semantics in
> types to tell you what a function will do, and since we curry it is
> not always clear in which order we will argument.

To be clear, I implemented search by type in order to understand a bit
more the book of Roberto Di Cosmo about type isomorphisms. Whether it
can be a useful tool remains to be determined. The tool now exists,
let's see if there is a usage for it.

I do agree that there is often not enough semantics in OCaml types, but
please notice that the order of arguments and whether the function is
currified is not relevant. Indeed, doing type search up to isomorphisms
allows to get rid of these details, all of the following queries will
answer with "String.sub":
   - "int -> int -> string -> string"
   - "string -> (int * int) -> string"
   - "string * int *int -> string"
while the actual signature is "string -> int -> int -> string".


Regards,

Xavier Clerc



  reply	other threads:[~2011-11-04 12:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 18:29 forum
2011-11-03  8:08 ` David MENTRE
2011-11-03 18:14   ` forum
2011-11-03 20:15     ` Fabrice Le Fessant
2011-11-04  9:24       ` rixed
2011-11-04  9:34         ` Anil Madhavapeddy
2011-11-04  9:47         ` Thomas Gazagnaire
2011-11-04 11:25           ` Daniel Bünzli
2011-11-04 12:45             ` forum [this message]
2011-11-04 13:03               ` Daniel Bünzli
2011-11-04 17:08             ` Romain Bardou
2011-11-04 18:05               ` Daniel Bünzli
2011-11-04 18:12                 ` Thomas Gazagnaire
2011-11-04  9:55         ` Fabrice Le Fessant
2011-11-04 13:26           ` Edgar Friendly
2011-11-04 10:18 ` Gerd Stolpmann
2011-11-04 12:30   ` forum

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=20111104134547.14475ul9wx5myyrk@ssl0.ovh.net \
    --to=forum@x9c.fr \
    --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).