From: Keiko Nakata <keiko@kurims.kyoto-u.ac.jp>
To: garrigue@math.nagoya-u.ac.jp
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Recursive types
Date: Thu, 17 Nov 2005 10:45:59 +0900 (JST) [thread overview]
Message-ID: <20051117.104559.68536741.keiko@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <20051116.175512.27779356.garrigue@math.nagoya-u.ac.jp>
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
> No need to memorize equivalences: s tuple expands at its head to s * s.
> The type checker guarantees that it is always safe to expand the head
> of a type (i.e., definitions are well-founded.)
Thanks for the reply.
> In order for unification to succeed above, t must expand to
> (< m: 'a * 'a> as 'a), and s too. But to print nicely types we must
> keep the abbreviations. This is done by memoizing expansions inside
> the abbreviations themselves.
This is a pretty nice feature of the type checker.
When programming with polymorphic variants,
the last part of typing error messages,
which tells me incompatibilities of types using abbreviating names,
always helps me a lot.
With best regards,
Keiko
next prev parent reply other threads:[~2005-11-17 1:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050506044107.1698.70519.Mailman@yquem.inria.fr>
2005-11-15 22:44 ` Swaroop Sridhar
2005-11-15 23:40 ` [Caml-list] " Jacques Garrigue
2005-11-16 2:20 ` Keiko Nakata
2005-11-16 6:47 ` Alain Frisch
2005-11-16 7:40 ` Keiko Nakata
2005-11-16 8:55 ` Jacques Garrigue
2005-11-17 1:45 ` Keiko Nakata [this message]
2005-11-16 3:28 ` Swaroop Sridhar
2005-11-16 8:38 ` Jacques Garrigue
2005-11-16 23:00 ` Swaroop Sridhar
2005-11-16 23:56 ` Swaroop Sridhar
2008-03-24 3:16 recursive types Jacques Le Normand
2008-03-24 3:51 ` [Caml-list] " Erik de Castro Lopo
2008-03-24 3:51 ` Erik de Castro Lopo
2008-03-24 8:37 ` Jeremy Yallop
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 9:44 nakata keiko
2004-12-13 9:58 ` [Caml-list] " Damien Pous
2004-12-13 12:31 ` skaller
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=20051117.104559.68536741.keiko@kurims.kyoto-u.ac.jp \
--to=keiko@kurims.kyoto-u.ac.jp \
--cc=caml-list@yquem.inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
/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).