From: "AUGER Cédric" <sedrikov@gmail.com>
To: oliver <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] "Modules Matter Most"
Date: Tue, 28 Feb 2012 13:46:49 +0100 [thread overview]
Message-ID: <20120228134649.33962978@gmail.com> (raw)
In-Reply-To: <20120227143809.GC2778@siouxsie>
Le Mon, 27 Feb 2012 15:38:09 +0100,
oliver <oliver@first.in-berlin.de> a écrit :
> Hello,
>
>
> this article I like.
> I also have experienced, that thinking in types
> (or: thinking in signatures) give a big advantage
> on planning a program, and later implementing it.
>
> Types make things very clear: you know what is input
> and what output and how things need to fit tigether,
> and what kind of signature is needed to maybe fill
> a gap between an input and an output module... just look
> at the missing link as a signature.
>
> Thie article also mentiones modules as a key point
> of OCaml, and I fully agree here:
>
> Modules Matter Most
> http://existentialtype.wordpress.com/2011/04/16/modules-matter-most/
>
>
> Ciao,
> Oliver
>
I find the posts on this blogs too much Ocaml biased. Ok, haskell has
not modules and it is somewhat missing, but using TypeFamilies, you can
emulate modules (and even 1st order modules which are available in Ocaml
only since 3.11 or 3.12), and in the other hand there is still not yet
any convenient way to have type classes in Ocaml. And it is not very
often that I would like to implement a module where a simple type class
wouldn't fit.
Are type classes planned in the future (and if not, what are the
reasons not to have it)?.
next prev parent reply other threads:[~2012-02-28 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 14:38 oliver
2012-02-28 12:46 ` AUGER Cédric [this message]
2012-02-28 19:42 ` Abdallah Saffidine
2012-03-05 2:25 ` Milan Stanojević
2012-03-05 8:57 ` AUGER Cédric
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=20120228134649.33962978@gmail.com \
--to=sedrikov@gmail.com \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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