From: Remi Vanicat <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] inference engine
Date: Sun, 21 Sep 2003 22:43:27 +0200 [thread overview]
Message-ID: <87he35g9e8.dlv@wanadoo.fr> (raw)
In-Reply-To: <1064162741.12854.73.camel@pelican> (skaller@ozemail.com.au's message of "22 Sep 2003 02:45:42 +1000")
skaller <skaller@ozemail.com.au> writes:
[...]
> [Where that's the line number of the place the inference
> was made]
>
> I can understand that inferences are incremental, and there
> would be a lot of pain tracking *all* the places the data came
> from to make a type inference: I'm not suggesting that.
One could use the new ocaml option -dtype and .annot file, and the
emacs mode that come with. I've never try it yet, but it give type
information inside a source, even if the source does not compile.
> Instead, I tried to suggest that somehow the constraint
> be included as early as possible. Clearly here that is NOT
> the case, or the error would have been detected where
> it actually occured.
there is a problem : one can have a .ml containing :
let f x = x + 1
let f x y = string_of_int (f x) ^ y
and the .mli :
val f : int -> string -> string
then applying the constraint of the .mli to the .ml became difficult
(at least).
but of course it could be doable.
In such a case I put the constraint into the .ml, helping me to narrow
the error.
[...]
--
Rémi Vanicat
remi.vanicat@laposte.net
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-09-21 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 6:58 skaller
2003-09-13 10:01 ` David Baelde
2003-09-14 4:12 ` skaller
2003-09-14 9:29 ` Remi Vanicat
2003-09-14 9:48 ` Alain.Frisch
2003-09-16 19:46 ` skaller
2003-09-21 16:45 ` skaller
2003-09-21 20:43 ` Remi Vanicat [this message]
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=87he35g9e8.dlv@wanadoo.fr \
--to=vanicat@labri.u-bordeaux.fr \
--cc=caml-list@inria.fr \
/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