From: Frank Atanassow <franka@cs.uu.nl>
To: John Max Skaller <skaller@ozemail.com.au>
Cc: Mattias Waldau <mattias.waldau@abc.se>, Caml-List <caml-list@inria.fr>
Subject: Re: Functions must be explicitly typed, (was Same label in different types, how do people solve this?)
Date: Fri, 15 Dec 2000 13:50:34 +0100 [thread overview]
Message-ID: <20001215135034.A4008@cs.uu.nl> (raw)
In-Reply-To: <3A36C815.EBA9AE89@ozemail.com.au>; from skaller@ozemail.com.au on Wed, Dec 13, 2000 at 11:51:33AM +1100
John Max Skaller wrote (on 13-12-00 11:51 +1100):
> In Ocaml, terse expression with the _option_ of adding a type
> constraint isn't that unreasonable. The real problem is that
> the inference engine isn't smart enough to remember _how_ it
> deduced a type, and report _both_ locations when there is a
> conflict. I have a suspicion this is non-trivial: probably
> worth a PhD. :-)
Or at least a Master's. And by a fortuitous coincidence, one of our students
Bastiaan Heeren wrote a thesis on this essentially this topic. His type
inferencer uses heuristics to improve the quality of type-error messages; for
example, if x gets assigned type A in 2 places, and type B in only 1 place,
then the inferencer reports the latter as the source of the type conflict.
You can find his page, and the thesis, here:
http://www.cs.uu.nl/people/bastiaan/
There is also some work by Dominic Duggan and Frederick Bent on "type
explanation":
D. Duggan and Frederick Bent. Explaining type inference. Science of
Computer Programming, 27,1, June 1996.
Dominic Duggan. Correct Type Explanations ACM ML Workshop, Baltimore,
Maryland, September 1998.
and an implementation, SML/E: A Type Explanation Facility for Standard ML:
http://guinness.cs.stevens-tech.edu/~dduggan/Public/Smle/index.html
--
Frank Atanassow, Information & Computing Sciences, Utrecht University
Padualaan 14, PO Box 80.089, 3508 TB Utrecht, Netherlands
Tel +31 (030) 253-3261 Fax +31 (030) 251-379
next prev parent reply other threads:[~2000-12-15 13:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 21:22 Same label in different types, how do people solve this? Mattias Waldau
2000-12-07 16:49 ` John Max Skaller
2000-12-07 18:34 ` Maxence Guesdon
2000-12-07 23:02 ` Gerd Stolpmann
2000-12-08 1:22 ` Jacques Garrigue
2000-12-08 9:31 ` Sven LUTHER
2000-12-08 9:36 ` Pierre Weis
2000-12-08 9:48 ` Sven LUTHER
2000-12-08 18:41 ` John Max Skaller
2000-12-08 9:40 ` Nicolas barnier
2000-12-08 16:36 ` Brian Rogoff
2000-12-11 17:19 ` Pierre Weis
2000-12-10 12:49 ` Mattias Waldau
2000-12-11 18:23 ` Chris Hecker
2000-12-11 19:17 ` Pierre Weis
2000-12-12 10:02 ` Sven LUTHER
2000-12-12 3:25 ` Chet Murthy
2000-12-12 17:43 ` John Max Skaller
2000-12-12 19:24 ` Functions must be explicitly typed, (was Same label in different types, how do people solve this?) Mattias Waldau
2000-12-13 0:51 ` John Max Skaller
2000-12-15 10:13 ` Andreas Rossberg
2000-12-15 12:50 ` Frank Atanassow [this message]
2000-12-14 18:42 ` Stefan Monnier
2000-12-15 12:47 ` Pierre Weis
2000-12-15 13:39 ` Mattias Waldau
2000-12-15 23:37 ` Brian Rogoff
2000-12-16 14:10 ` ROverloading John Max Skaller
2000-12-15 21:51 ` Same label in different types, how do people solve this? Bruce Hoult
2000-12-12 17:19 ` John Max 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=20001215135034.A4008@cs.uu.nl \
--to=franka@cs.uu.nl \
--cc=caml-list@inria.fr \
--cc=mattias.waldau@abc.se \
--cc=skaller@ozemail.com.au \
/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).