From: Brian Hurt <bhurt@janestcapital.com>
To: William W Smith <sesquized@sbcglobal.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] type abbreviation is cyclic
Date: Wed, 24 Oct 2007 13:44:28 -0400 [thread overview]
Message-ID: <471F847C.1050609@janestcapital.com> (raw)
In-Reply-To: <344522.90449.qm@web82102.mail.mud.yahoo.com>
William W Smith wrote:
> I wonder whether this error is an example of the language being
> defined more restrictively than required. What is the reason that I
> get these results?
>
> type a = int -> one -> int and one = Unused | One of a;;
> type b = int -> b -> int
>
> type a is accepted while type b is not. (b gives "The type
> abbreviation b is cyclic" However, in the uses that I intended, there
> won't be any actual difference between the two.
>
> I'd appreciate an explanation about why there is difference between a
> and b.
I *think* this has to do with being able to bottom out data structures.
I mean, consider the following two (similiar) types:
type a = int * one * int and one = Unused | One of a;;
type b = int * b * int;;
How do you specify a limited-length member of type b? You can with a
just by inserting Unused in the correct location. But there's no such
"stopping point" for b.
This makes more sense when you make the linked-list aspect more plain:
type a = int * next and next = EmptyList | Cons of a;;
type b = int * b;;
Hopefully someone more knowledgeable than I will post an actual
type-theoretical reason this is so, but this is the pragmatic reason
I've found.
Brian
next prev parent reply other threads:[~2007-10-24 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 17:27 William W Smith
2007-10-24 17:40 ` [Caml-list] " Till Varoquaux
2007-10-24 22:01 ` Dmitri Boulytchev
2007-10-24 17:44 ` Brian Hurt [this message]
2007-10-24 18:09 ` Till Varoquaux
2007-10-24 20:40 ` Jon Harrop
2007-10-25 1:34 ` Dmitri Boulytchev
2007-10-24 21:36 ` Dmitri Boulytchev
2007-10-24 21:38 ` Dmitri Boulytchev
2007-10-25 11:22 William Smith
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=471F847C.1050609@janestcapital.com \
--to=bhurt@janestcapital.com \
--cc=caml-list@yquem.inria.fr \
--cc=sesquized@sbcglobal.net \
/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;
as well as URLs for NNTP newsgroup(s).