caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois BERENGER <francois.c.berenger@vanderbilt.edu>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] where are we on the Hoogle for OCaml front?
Date: Mon, 6 Feb 2017 11:46:25 -0600	[thread overview]
Message-ID: <75259477-c014-b7b7-26b1-8519e4c6d2f5@vanderbilt.edu> (raw)
In-Reply-To: <67BCE44C836B466EBD22FC5CE5A4CD13@erratique.ch>

On 02/06/2017 09:46 AM, Daniel Bünzli wrote:
> On Saturday, 4 February 2017 at 04:58, Jacques Garrigue wrote:
>> For search by type signature you can use Jun Furuse's OCamlOScope:
>
> I'm a little bit curious. While I can see the benefit of having general full text search over value identifiers, type identifier and doc strings I was always a little bit dubious about type signature search -- in the end ML types for themselves are a rather weak specification language (I'm not talking about the invariants you may hide behind those of course).

For sure, a plain text search is also very useful and should be provided 
by such a tool (a search "a la Google"; by keywords).

> So beyond curiosity searches are actually people seriously using this to lookup a value they might need ?

But, when you have no idea of how people call the function you are 
looking for, you would go for the search by type signature.

And, because you are not lucky every time, the "hoogle for ocaml" should 
also give you interesting results even when the type signature you have 
input contains some errors.
Like, if the type signature you typed does not exist, you may be 
interested by the closest matching type signature.

      parent reply	other threads:[~2017-02-06 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 14:22 [Caml-list] FroCoS 2017 - 2nd Call for Papers Geoff Sutcliffe
2017-01-27 16:39 ` [Caml-list] where are we on the Hoogle for OCaml front? Francois BERENGER
2017-02-04  3:58   ` Jacques Garrigue
2017-02-06 14:35     ` Francois BERENGER
2017-02-06 15:46     ` Daniel Bünzli
2017-02-06 14:02       ` Hendrik Boom
2017-02-06 16:00         ` Daniel Bünzli
2017-02-06 16:07           ` Ivan Gotovchits
2017-02-06 16:11             ` Ivan Gotovchits
2017-02-06 16:34             ` Daniel Bünzli
2017-02-06 16:46               ` Ivan Gotovchits
2017-02-06 16:55                 ` Frédéric Bour
2017-02-06 16:01         ` Ivan Gotovchits
2017-02-06 16:06           ` Daniel Bünzli
2017-02-06 17:46       ` Francois BERENGER [this message]

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=75259477-c014-b7b7-26b1-8519e4c6d2f5@vanderbilt.edu \
    --to=francois.c.berenger@vanderbilt.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).