From: j h woodyatt <jhwoodyatt@mac.com>
To: The Caml Trade <caml-list@inria.fr>
Subject: [Caml-list] Re: Phantom types (very long)
Date: Tue, 11 Sep 2001 11:38:08 -0700 [thread overview]
Message-ID: <25775F60-A6E4-11D5-9E93-000502DB38F5@mac.com> (raw)
In-Reply-To: <20010910154559.O6031-100000@shell5.ba.best.com>
So okay... I take it back. Caml *does* have invariants. (I'm
learning. Slowly. But I'm learning.)
This "phantom types" design pattern is one I have never seen before. It
doesn't seem to be used in the standard library anywhere I can see. It
looks like it might be useful in presenting a safer network programming
interface than the low-level wrappers around BSD sockets (which I've
never liked).
Are there any other mind-blowingly elegant design patterns lurking in
the corners of the Caml type inference engine that I should know about?
--
j h woodyatt <jhw@wetware.com>
"You're standing on sacred ground. Many strange and wonderful
things have transpired right where you're standing."
--unattributable
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-11 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 18:35 [Caml-list] opaque polymorphism Charles Martin
2001-09-10 7:02 ` Francois Pottier
2001-09-10 23:19 ` Phantom types (very long) (Was Re: [Caml-list] opaque polymorphism) Brian Rogoff
2001-09-11 9:44 ` Andreas Rossberg
2001-09-11 18:38 ` j h woodyatt [this message]
2001-09-11 19:16 ` [Caml-list] Re: Phantom types (very long) Brian Rogoff
2001-09-12 9:33 ` Daan Leijen
2001-09-14 8:49 ` Jacques Garrigue
2001-09-14 19:10 ` Brian Rogoff
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=25775F60-A6E4-11D5-9E93-000502DB38F5@mac.com \
--to=jhwoodyatt@mac.com \
--cc=caml-list@inria.fr \
--cc=jhw@wetware.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