caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] different records, same field name?
Date: Mon, 3 Mar 2008 22:29:23 +0000	[thread overview]
Message-ID: <200803032229.24345.jon@ffconsultancy.com> (raw)
In-Reply-To: <200803031432.03002.ober.14@osu.edu>

On Monday 03 March 2008 19:32:02 Kuba Ober wrote:
> I think that type inference in OCaml sometimes gets in the way of other
> language features. I'd much rather see OCaml go in a direction where type
> inference is performed on "as far as it can go" basis.

Other languages already do that, of course, and it just brings a different set 
of trade-offs. OCaml is roughly the best you can get in this respect.

Breaking decideability seems like a bad idea because you end up annotating all 
types and benefitting much less from type inference, as is idiomatic in 
Haskell and imposed in Scala.

The alternative of flagging an error when an ambiguity arises is used by F# 
but it makes no attempt to search current definitions for structurally- 
compatible classes. Indeed, I already find it confusing and a little ugly to 
have to add type annotations as you develop because your final product often 
ends up with unnecessary annotations as later developments remove 
ambiguities.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  parent reply	other threads:[~2008-03-03 23:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 16:51 mfmorss
2008-03-03 16:53 ` [Caml-list] " Jon Harrop
2008-03-03 16:55 ` Basile STARYNKEVITCH
2008-03-03 19:32   ` Kuba Ober
2008-03-03 21:04     ` Michael Wohlwend
2008-03-03 22:29     ` Jon Harrop [this message]
2008-03-03 18:45 ` DooMeeR
2008-03-04  9:52   ` Berke Durak
2008-03-04 10:25     ` David Teller

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=200803032229.24345.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).