From: Francois BERENGER <francois.c.berenger@vanderbilt.edu>
To: <caml-list@inria.fr>
Subject: [Caml-list] where are we on the Hoogle for OCaml front?
Date: Fri, 27 Jan 2017 10:39:42 -0600 [thread overview]
Message-ID: <416beaa2-9430-20fe-d8fa-e9f02761378f@vanderbilt.edu> (raw)
In-Reply-To: <20170127142246.919C212146E@mcclellan.cs.miami.edu>
Hello,
Do we have a hoogle[1] equivalent that is in production for OCaml?
I mean something that would index all source code available in opam
and allow queries by type signature or keyword?
Currently, I use ocp-browser but I still feel like
it's a temporary and not super efficient measure.
I don't know how to do query by type signature with it.
And many packages don't install their doc so you cannot
see the doc for each function.
At list for the stdlib it works (inside ocp-browser you type List.map
then spacebar, for example).
When I was an Haskell programmer (for two months, a long time ago), I
felt Hoogle was the biggest productivity enhancer (you don't reinvent
the wheel, just find which one you need and use it).
Regards,
F.
[1] https://www.haskell.org/hoogle/
next prev parent reply other threads:[~2017-01-27 16:40 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 ` Francois BERENGER [this message]
2017-02-04 3:58 ` [Caml-list] where are we on the Hoogle for OCaml front? 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
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=416beaa2-9430-20fe-d8fa-e9f02761378f@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