From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Ivan Gotovchits <ivg@ieee.org>
Cc: Hendrik Boom <hendrik@topoi.pooq.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] where are we on the Hoogle for OCaml front?
Date: Mon, 6 Feb 2017 17:34:00 +0100 [thread overview]
Message-ID: <F9785305E6E44CB2884E939A04EBBA39@erratique.ch> (raw)
In-Reply-To: <CALdWJ+wjP=u3djyNahW=o3c_yp9BNtacx=40San65yW6ip=6UA@mail.gmail.com>
On Monday, 6 February 2017 at 17:07, Ivan Gotovchits wrote:
> That's why the search should be up-to some isomorphism, e.g.,
>
> int -> float -> bool
>
>
> is isomoprhic to
>
> float -> int -> bool
The papers you mention seem to be about the type ismorophism theory but I can't see any that tries to asses end-user information needs and retrieval evaluation. I'm not sure you need the full theory to build an effective system to support a programmer, e.g. what about the effectiveness of a full type isomorphism search vs a bag of type identifiers with functional position model. Meaningfully limiting the query power to an IR system is a problem in practice, for space, computational and user interface reasons.
D
next prev parent reply other threads:[~2017-02-06 16:34 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 [this message]
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=F9785305E6E44CB2884E939A04EBBA39@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.com \
--cc=ivg@ieee.org \
/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