From: Peter Thiemann <thiemann@informatik.uni-freiburg.de>
To: "François Pottier" <francois.pottier@inria.fr>
Cc: Peter Thiemann <thiemann@informatik.uni-freiburg.de>,
Andreas Rossberg <rossberg@mpi-sws.org>,
caml-list@inria.fr
Subject: Re: [Caml-list] coinductive data types
Date: Wed, 31 Aug 2022 10:46:57 +0200 [thread overview]
Message-ID: <EE42D89E-519E-4315-84A6-2DE34C292685@informatik.uni-freiburg.de> (raw)
In-Reply-To: <99c919e0-95aa-2c4f-7240-71486da1fb65@inria.fr>
Hi François and Andreas,
this is an interesting question, which we also ran into quite recently.
Algebraic datatypes seem to conflate the isomorphism for the recursive type with the injection into a sum-of-product type for the constructors.
They give rise to nominal types, not structural.
They are certainly not equi-recursive, because they are not equal to their unfolding.
I'd also call them iso-recursive or should they be a category by themselves?
Best
-Peter
> On 31. Aug 2022, at 10:25, François Pottier <francois.pottier@inria.fr> wrote:
>
>
> Hi Andreas,
>
> Le 30/08/2022 à 18:45, Andreas Rossberg a écrit :
> > I’m curious why you would categorise iso-recursive types as nominal. I have always considered them structural as well, since two structurally matching iso-recursive type expressions are still deemed equivalent.
>
> I had in mind a system with algebraic data types, which have a name, and where
> two algebraic data types with distinct names can never be related by subtyping.
>
> In such a system, an algebraic data type is *not* equal to its unfolding, which
> is why I used the word "iso-recursive".
>
> It is quite possible that I used the wrong word, and should not have referred
> to such types as "iso-recursive".
>
> --
> François Pottier
> francois.pottier@inria.fr
> http://cambium.inria.fr/~fpottier/
next prev parent reply other threads:[~2022-08-31 8:47 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
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 [this message]
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=EE42D89E-519E-4315-84A6-2DE34C292685@informatik.uni-freiburg.de \
--to=thiemann@informatik.uni-freiburg.de \
--cc=caml-list@inria.fr \
--cc=francois.pottier@inria.fr \
--cc=rossberg@mpi-sws.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