caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jun Furuse <jun.furuse@gmail.com>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] OCamlOScope: a new OCaml API search
Date: Mon, 8 Jul 2013 23:42:39 +0800	[thread overview]
Message-ID: <CAAoLEWvOC8brxFBG2XiU_AOzW0M2eON=A6XxGvV2nvvo6eAEGA@mail.gmail.com> (raw)
In-Reply-To: <CACLX4jQYGnKJc5UFDfu_STfw5DaM6LYFdq2sW2T31ZRxdRd0+Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]

Hi Yaron,

I have just updated it so that it expands manifest types. It is a dirty
hack but "split : string -> char -> string list" lists up
Core.Std.String.Escaping.split.

There are still lots of things to do before it becomes as powerful as
Hoogle is, but so far, I am working on its speed and size rather than
search quality.

Jun


On Fri, Jul 5, 2013 at 11:25 AM, Yaron Minsky <yminsky@janestreet.com>wrote:

> Neat!
>
> I played with it for a bit, and the main issue it saw with it is the
> trickiness around type names for things like string.  For example, to find
> core or batteries' string split function, you need to search for
>
> t -> char -> t list
>
> Rather than
>
> string -> char -> string list
>
> Which finds ocplib's equivalent, and the Core.Std.String.Escaping version
> as well.
>
> Fill on unification doesn't seem ideal, but I wonder if some ability to
> recognize equivalent type names can be done without full-on search time
> unification.
> On Jul 5, 2013 5:12 AM, "Jun Furuse" <jun.furuse@gmail.com> wrote:
>
>> Hi list,
>>
>> I have launched a new OCaml API search, OCaml◎Scope at
>> http://ocamloscope.herokuapp.com .
>>
>> OCaml◎Scope is a type directed library search, derived work from OCaml
>> API Search by Mizuno and its ancestor OCamlBrowser by Garrigue. It is also
>> inspired from Hoogle, the same API search engine for Haskell by MItchell,
>> which I regularly use in my Haskell :-) job.
>>
>> * Fast and Portable. It loads everything in memory, unlike OCaml API
>> Search and OCamlBrowser which load compiled interface files (*.cmi)
>> dynamically. The data file is extracted from compiled files but
>> self-contained, so the search engine does not require to compile the
>> libraries locally.
>> * No use of unification but edit distance of types like Hoogle.
>> Unification does not provide good results in type directed search, and is
>> costy.
>> * OCamlFind and OPAM friendly. OCaml◎Scope knows which items are from
>> which OCamlFind and OPAM packages.
>> * OCamlDoc: it also extracts OCamlDoc comments, if possible.
>> * Small: it can even run as a heroku app. Currently it carries 245k
>> entries from 76 OCamlFind packages including Core and Batteries, but the
>> data file (as a marshalled OCaml value) is still 20Mb.
>>
>> There are lots of todos but I think the search results look well sane so
>> far. If you find something strange please drop by
>> https://bitbucket.org/camlspotter/ocamloscope-server/issues?status=new&status=open and
>> leave some comments. Thanks!
>>
>> Jun Furuse
>>
>>

[-- Attachment #2: Type: text/html, Size: 3691 bytes --]

  reply	other threads:[~2013-07-08 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05  2:11 Jun Furuse
2013-07-05  3:25 ` Yaron Minsky
2013-07-08 15:42   ` Jun Furuse [this message]
2013-07-05 14:51 ` Ashish Agarwal
2013-07-08 15:47   ` Jun Furuse
2013-07-08  0:51 ` Francois Berenger
2013-07-08 16:06   ` Jun Furuse
2013-07-08 18:58     ` Gerd Stolpmann

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='CAAoLEWvOC8brxFBG2XiU_AOzW0M2eON=A6XxGvV2nvvo6eAEGA@mail.gmail.com' \
    --to=jun.furuse@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=yminsky@janestreet.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;
as well as URLs for NNTP newsgroup(s).