From: Michael Vanier <mvanier@cs.caltech.edu>
To: checker@d6.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] "high end" type theory for working programmers?
Date: Thu, 2 May 2002 18:36:50 -0700 [thread overview]
Message-ID: <200205030136.g431ao611142@orchestra.cs.caltech.edu> (raw)
In-Reply-To: <4.3.2.7.2.20020502173934.03b73250@mail.d6.com> (message from Chris Hecker on Thu, 02 May 2002 17:49:25 -0700)
I highly recommend Benjamin Pierce's new book "Types in Programming
Languages" from MIT press. It's very well-written, covers much of the
material you describe, and includes implementations in ocaml ;-)
Mike
> Date: Thu, 02 May 2002 17:49:25 -0700
> From: Chris Hecker <checker@d6.com>
>
> The list has had a lot of discussions about type theory behind the module
> system, tuples, and the like lately. Most of it has been over my head,
> which is fun, because it presents a challenge to try to figure out what
> people are saying. I am wondering how much of it is useful for actually
> writing "regular" code (as opposed to compilers or theorem provers). Are
> there books (or survey papers) on this stuff that are meant to educate
> working programmers, as opposed to language researchers? For example,
> where should I go to learn what this means, and whether I care (just a
> randomly chosen sentence representative of stuff that's currently over my
> head from the past few days on the list):
>
> "That functor is essentially the polymorphic identity functor, while the
> other variation was a polymorphic eta-expansion of the abstraction operator."
>
> or another example:
>
> "In this encoding, modules are only records, so module types are ordinary
> types, and there is no distinction between ordinary abstract types
> (introduced by explicit polymorphic abstraction) and ``abstract
> signatures''. There is, as far as I can tell, no need for kind polymorphism."
>
> I started using caml to find out if a "higher level" language could make a
> difference in my programming productivity (writing video games). As I
> continue with that experiment, I'm curious to know whether understanding
> this high end type theory stuff would help make me a better programmer, or
> just more able to understand the list lately. Either is fine, but both
> would obviously be great. :)
>
> Chris
>
-------------------
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-03 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 0:49 Chris Hecker
2002-05-03 1:36 ` Michael Vanier [this message]
2002-05-03 4:52 ` Will Benton
2002-05-03 12:57 Krishnaswami, Neel
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=200205030136.g431ao611142@orchestra.cs.caltech.edu \
--to=mvanier@cs.caltech.edu \
--cc=caml-list@inria.fr \
--cc=checker@d6.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