From: "David Allsopp" <dra-news@metastack.com>
To: "'Jacques Garrigue'" <garrigue@math.nagoya-u.ac.jp>
Cc: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] What is a future of ocaml?
Date: Thu, 15 Jan 2009 12:51:07 -0000 [thread overview]
Message-ID: <00b301c9770f$efc241b0$cf46c510$@com> (raw)
In-Reply-To: <20090115.211335.27794984.garrigue@math.nagoya-u.ac.jp>
Jacques Garrigue wrote:
> The reason is mostly wrong :-)
That'll teach me to comment on type theory on this list :o)
> And neither polymorphic variants nor object require type anotations in
> ocaml; they just make it much more painful to understand error
> messages.
Though I'm confused by this - I thought that polymorphic methods in classes
(a part of the object system) do require type annotations and there are
cases with polymorphic variants where coercions (which I'd regard as a type
annotation?) must be explicitly written for a valid program to type. I
wasn't trying to say that all uses of them require type annotations, just
that there are occasions where you *have* to use them whereas for "core" ML
you never *have* to include a type annotation for *any* valid program - your
types just might be more general than you expect/want.
Or am I still barking up the wrong tree?
David
next prev parent reply other threads:[~2009-01-15 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 9:18 Radzevich Belevich
2009-01-14 9:35 ` [Caml-list] " David Allsopp
2009-01-14 9:51 ` Richard Jones
2009-01-14 13:34 ` Sylvain Le Gall
2009-01-14 13:44 ` [Caml-list] " Dawid Toton
2009-01-14 15:37 ` Martin Jambon
2009-01-14 15:39 ` David Allsopp
2009-01-15 12:13 ` Jacques Garrigue
2009-01-15 12:46 ` Benedikt Grundmann
2009-01-15 22:20 ` Oliver Bandel
2009-01-16 14:56 ` Kuba Ober
2009-01-15 12:51 ` David Allsopp [this message]
2009-01-15 21:08 ` Stefan Monnier
2009-01-14 16:07 ` [Caml-list] " Jérémie Dimino
2009-01-14 17:28 ` Dario Teixeira
2009-01-15 17:50 ` Richard Jones
2009-01-15 17:46 ` Richard Jones
2009-01-18 16:34 ` Xavier Leroy
2009-01-18 18:02 ` Richard Jones
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='00b301c9770f$efc241b0$cf46c510$@com' \
--to=dra-news@metastack.com \
--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).