From: Ching-Tsun Chou <ctchou@mipos2.intel.com>
To: pixel@mandrakesoft.com
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Weird typing problem
Date: Tue, 21 May 2002 16:20:11 -0700 (PDT) [thread overview]
Message-ID: <200205212320.g4LNKBQ27191@zws707.sc.intel.com> (raw)
In-Reply-To: <lyy9ed6r34.fsf@leia.mandrakesoft.com> (message from Pixel on 22 May 2002 01:03:59 +0200)
Thanks! But I still fail to see why the compiler and the interpreter
should behave differently.
- Ching Tsun
X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f
Cc: caml-list@pauillac.inria.fr
From: Pixel <pixel@mandrakesoft.com>
Date: 22 May 2002 01:03:59 +0200
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Content-Type: text/plain; charset=us-ascii
Sender: owner-caml-list@pauillac.inria.fr
Precedence: bulk
Ching-Tsun Chou <ctchou@mipos2.intel.com> writes:
[...]
> let list_last = List.hd << List.rev
[...]
> val list_last : '_a list -> '_a = <fun>
make it:
let list_last l = (List.hd << List.rev) l
val list_last : 'a list -> 'a
that's monomorphism restriction:
http://caml.inria.fr/FAQ/FAQ_EXPERT-eng.html#variables_de_types_faibles
-------------------
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
-------------------
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
next prev parent reply other threads:[~2002-05-21 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 22:13 Ching-Tsun Chou
2002-05-21 23:03 ` Pixel
2002-05-21 23:20 ` Ching-Tsun Chou [this message]
2002-05-21 23:48 Ryan Tarpine
[not found] <F143h1mIs1Dk3fqSUVd000021b5@hotmail.com>
2002-05-21 23:58 ` Ching-Tsun Chou
2002-05-22 0:14 Ryan Tarpine
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=200205212320.g4LNKBQ27191@zws707.sc.intel.com \
--to=ctchou@mipos2.intel.com \
--cc=caml-list@pauillac.inria.fr \
--cc=pixel@mandrakesoft.com \
/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).