Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: brogoff <brogoff@speakeasy.net>
To: skaller <skaller@users.sourceforge.net>
Cc: Jon Harrop <jon@ffconsultancy.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] parameterized pattern
Date: Thu, 9 Nov 2006 08:22:01 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0611090757440.27097@shell2.speakeasy.net> (raw)
In-Reply-To: <1163062280.28049.110.camel@rosella.wigram>

On Thu, 9 Nov 2006, skaller wrote:
> On Thu, 2006-11-09 at 05:19 +0000, Jon Harrop wrote:
> > On Thursday 09 November 2006 01:45, brogoff wrote:
> > > It's a pity, as I've often wished that OCaml supported the extensional
> > > polymorphism that GCaml has, but I don't think that's going to happen.
> > > It would probaby make more sense to create a separate language at this
> > > point, since OCaml is complicated enough.
> >
> > I think F# provides some form of extensional polymorphism.

I just did a quick scan of some F# docs and I saw nothing. What did you have in
mind?

> > I'm not convinced that it is a good idea yet...

For almost any given language feature, there will be people who like it, and
people who don't. Do you think having class based OO in OCaml is a good idea?
I find it useful, especially since OCaml records are far too restrictive, but
I hope that in some future ML that there are other approaches as the
class/object system is complex, and the interactions with "core ML + modules"
is tricky.

That said, the class system is being used and it won't go away, and some
people really like it.

> Well FYI Felix has traditional (open) overloading, but since it
> doesn't allow traditional C++ style dependent name lookup because
> that would destroy parametricity of polymorphic functions,
> something else was needed.
>
> So it now has first order typeclasses to solve this problem.

Did you consider GCaml style generic functions?

-- Brian


  reply	other threads:[~2006-11-09 16:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 21:15 Serge Aleynikov
2006-11-06 23:58 ` [Caml-list] " Jon Harrop
2006-11-07  0:12   ` Serge Aleynikov
2006-11-06 23:59 ` Martin Jambon
2006-11-08 23:55 ` Lukasz Stafiniak
2006-11-09  1:45   ` brogoff
2006-11-09  5:19     ` Jon Harrop
2006-11-09  8:51       ` skaller
2006-11-09 16:22         ` brogoff [this message]
2006-11-09 17:55           ` skaller
2006-11-14 23:12           ` Don Syme
2006-11-15  1:00             ` brogoff
2006-11-15  1:36               ` Don Syme
2006-11-09  5:18   ` Jon Harrop
2006-11-09 16:42     ` micha

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=Pine.LNX.4.58.0611090757440.27097@shell2.speakeasy.net \
    --to=brogoff@speakeasy.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.com \
    --cc=skaller@users.sourceforge.net \
    /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