Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Type inference and marshalling
Date: Wed, 6 Jul 2011 09:11:09 +0400 (MSD)	[thread overview]
Message-ID: <alpine.LNX.2.00.1107060909230.1433@linmac> (raw)
In-Reply-To: <098226D8-77AA-4F80-97A5-F72F47C6A98E@math.nagoya-u.ac.jp>

On Wed, 6 Jul 2011, Jacques Garrigue wrote:

> On 2011/07/05, at 22:59, malc wrote:
> 
> > Perhaps someone could explain why following behaves the way it does:
> > 
> > ~$ ocaml
> >        Objective Caml version 3.11.2
> > 
> > # let f ic = let i = input_value ic in let j = i + 1 in LargeFile.seek_in ic i;;
> > Warning Y: unused variable j.
> > val f : in_channel -> unit = <fun>
> 
> The return type of input_value being 'a, which gets generalized by the
> relaxed value restriction, i gets the polymorphic type "forall 'a. 'a".
> So you can use it both as an int and an int64.
> ==> input_value is an unsafe function, you should always write a type
> 	annotation on its return type.

Sure i'm well aware of that, but to me "let j = i + 1" means that i has
type int and after that "LargeFile.seek ic i" makes no sense yet is
accepted by the type checker.

> 
> > # let f ic = let i = input_value ic in let j = i + 1 in LargeFile.seek_in ic j;;
> > Error: This expression has type int but an expression was expected of type
> >         int64
> 
> j being the result of an integer addition, it has type int, and cannot be used
> as int64.
> 
> Jacques
> 
> 

-- 
mailto:av1474@comtv.ru

  reply	other threads:[~2011-07-06  5:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 13:59 malc
2011-07-05 14:18 ` Wojciech Meyer
2011-07-05 14:54   ` Mathias Kende
2011-07-05 23:24 ` Jacques Garrigue
2011-07-06  5:11   ` malc [this message]
2011-07-06  7:44     ` Jacques Garrigue
2011-07-06  8:31       ` malc

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=alpine.LNX.2.00.1107060909230.1433@linmac \
    --to=av1474@comtv.ru \
    --cc=caml-list@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