Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Ivan Gotovchits <ivg@ieee.org>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
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 11:11:45 -0500	[thread overview]
Message-ID: <CALdWJ+yOkBH+T+tf6t9gBN0kNGV2wiB1x+JW+nXVaHLoteYN2Q@mail.gmail.com> (raw)
In-Reply-To: <CALdWJ+wjP=u3djyNahW=o3c_yp9BNtacx=40San65yW6ip=6UA@mail.gmail.com>

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

This is a link [1] to the underlying theory of type isomorphism search, for
those who are interested:

[1]: http://www.dicosmo.org/ResearchThemes/ISOS/ISOShomepage.html

On Mon, Feb 6, 2017 at 11:07 AM, Ivan Gotovchits <ivg@ieee.org> wrote:

>
>
> On Mon, Feb 6, 2017 at 11:00 AM, Daniel Bünzli <
> daniel.buenzli@erratique.ch> wrote:
>
>> On Monday, 6 February 2017 at 15:02, Hendrik Boom wrote:
>> > It is very useful to find all the
>> > functions that do anything with values of a particular type in order
>> > to find out what you can do with it. As well as how you can produce
>> > values of that type.
>>
>> Sure but boolean queries on type identifiers seems enough for this. Of
>> course you can always wish to be more precise --- I want this type to
>> appear in that position --- but I'm not sure that's an information need
>> users often have.
>
>
>
> That's why the search should be up-to some isomorphism, e.g.,
>
>      int -> float -> bool
>
>
> is isomoprhic to
>
>    float -> int -> bool
>
>
> The seach should also work correctly with lots of aliases, since it is
> usual when the same type or value in OCaml has mutliple names. The seach
> should also ignore parameter names,
> as this is not what a user can know in advance.
>
>
>
>>
>>
>> D
>>
>>
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
>

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

  reply	other threads:[~2017-02-06 16:11 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 [this message]
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=CALdWJ+yOkBH+T+tf6t9gBN0kNGV2wiB1x+JW+nXVaHLoteYN2Q@mail.gmail.com \
    --to=ivg@ieee.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=hendrik@topoi.pooq.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