Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Nate Foster <jnfoster@cs.cornell.edu>
To: Aaron Gray <aaronngray.lists@gmail.com>
Cc: "François Pottier" <francois.pottier@inria.fr>,
	"OCaML Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] coinductive data types
Date: Tue, 30 Aug 2022 09:57:52 -0400	[thread overview]
Message-ID: <CAH6P-srScCj+mteVDJBYPMKb1VmyhR7EyW1V5fGJBA4Sdmce-Q@mail.gmail.com> (raw)
In-Reply-To: <CANkmNDeFiieWNq0WEh0p52E61qHUJ2_BMH8int67uif+RrRAQw@mail.gmail.com>

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

Hi Aaron,

You might be interested in looking at CoCaml. It was developed by
Jean-Baptiste Jeannin as part of his PhD, in collaboration with his advisor
Dexter Kozen and Alexandra Silva.

https://www.cs.cornell.edu/Projects/CoCaml/

Cheers,
-N

On Tue, Aug 30, 2022 at 8:38 AM Aaron Gray <aaronngray.lists@gmail.com>
wrote:

> Hello François,
>
> Thanks for putting me straight on that.
>
> My original path of inquiry which I should have actually stated was
> regarding how to go about implementing subtyping of mutually recursive
> algebraic data types.
>
> I am looking on how to go about this and using coinduction and
> bisimulation seemed like the best fit or correct way to go about this.
>
> Does OCaML use/handle subtyping of mutually recursive algebraic data
> types ? And if so, is its implementation easily accessible ?
>
> Sorry I got you and Xavier muddled up somehow !
>
> Regards,
>
> Aaron
>
> On Tue, 30 Aug 2022 at 08:24, François Pottier
> <francois.pottier@inria.fr> wrote:
> >
> >
> > Hello,
> >
> > Le 29/08/2022 à 17:43, Aaron Gray a écrit :
> > > Does either ML or OCaML have coinductive data types ? And if so could
> > > you please point me at the/some appropriate documentation on them.
> >
> > ML and OCaml have algebraic data types, which are recursive (that is,
> > more general than inductive and co-inductive types). Algebraic data
> > type definitions are not subject to a positivity restriction, and
> > algebraic data types can be constructed and deconstructed by recursive
> > functions, which are not subject to a termination check.
> >
> > If you want to see a typical example of a "co-inductive" data structure
> > encoded in OCaml, I suggest to have a look at "sequences", which can be
> > described as potentially infinite lists:
> >
> >    https://v2.ocaml.org/api/Seq.html
> >
> > --
> > François Pottier
> > francois.pottier@inria.fr
> > http://cambium.inria.fr/~fpottier/
>
>
>
> --
> Aaron Gray
>
> Independent Open Source Software Engineer, Computer Language
> Researcher, Information Theorist, and amateur computer scientist.
>

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

  reply	other threads:[~2022-08-30 13:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 15:43 Aaron Gray
2022-08-30  7:24 ` François Pottier
2022-08-30 11:11   ` Xavier Leroy
2022-08-30 12:33     ` Aaron Gray
2022-08-31  1:21       ` Jacques Garrigue
     [not found]       ` <11E3A59A-BD33-4EC0-9FAD-711A1EACA35E@gmail.com>
2022-08-31  3:22         ` Aaron Gray
2022-09-01 12:13           ` Jacques Garrigue
2022-08-30 12:37   ` Aaron Gray
2022-08-30 13:57     ` Nate Foster [this message]
2022-08-30 15:27       ` Aaron Gray
2022-08-30 15:47     ` François Pottier
2022-08-30 16:32       ` Aaron Gray
2022-08-31  8:19         ` François Pottier
2022-08-30 16:45       ` Andreas Rossberg
2022-08-30 17:01         ` Aaron Gray
2022-08-30 18:20           ` Nate Foster
2022-08-31  8:25         ` François Pottier
2022-08-31  8:46           ` Peter Thiemann
2022-08-31  9:41             ` Andreas Rossberg
2022-08-31 13:49               ` François Pottier
2022-08-31 15:40               ` Peter Thiemann
2022-08-31 16:44                 ` Andreas Rossberg
2022-08-31 15:55               ` Basile Clement
2022-08-31 18:42                 ` Andreas Rossberg

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=CAH6P-srScCj+mteVDJBYPMKb1VmyhR7EyW1V5fGJBA4Sdmce-Q@mail.gmail.com \
    --to=jnfoster@cs.cornell.edu \
    --cc=aaronngray.lists@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=francois.pottier@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