From: Nathaniel Gray <n8gray@gmail.com>
To: skaller@users.sourceforge.net
Cc: David Brown <caml-list@davidb.org>,
Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Single-case union types as strong typedefs
Date: Sat, 23 Oct 2004 14:49:08 -0700 [thread overview]
Message-ID: <aee06c9e04102314495aa44fee@mail.gmail.com> (raw)
In-Reply-To: <1098507602.7584.163.camel@pelican.wigram>
On 23 Oct 2004 15:00:02 +1000, skaller <skaller@users.sourceforge.net> wrote:
> This:
> newtype metres = float
> meaning
> type metres = Metres float
>
> means you have to define all the operations on 'metres' all
> over again:
>
> let (++) (Metres x) (Metres y) = Metres (x .+ y)
>
> I'd guess in Haskell newtype can benefit from typeclasses?
I would have to try writing some code to be sure it makes sense, but I
envisioned this as more of a contract mechanism. It would be a way of
making "semi-opaque" values without encapsulation guarantees but also
without performance penalties. A function that needed to do any
serious work with the underlying values would destruct the wrappers:
let hypoteneuse (Metres x) (Metres y): metres = sqrt(x*x + y*y)
> Actually for quantities, you'd use some phantom types
> so you could represent products of the dimensions,
> such as square metres too .. so the simplistic
> constructor representation isn't very good.
I'll have to read a bit about phantom types. Maybe they fit the bill.
Cheers,
-n8
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
-------------------
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:[~2004-10-23 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:49 Nathaniel Gray
2004-10-23 3:31 ` Jacques Garrigue
2004-10-23 3:39 ` David Brown
2004-10-23 5:00 ` skaller
2004-10-23 21:49 ` Nathaniel Gray [this message]
2004-10-23 21:24 ` Nathaniel Gray
2004-10-23 21:33 ` Nathaniel Gray
2004-10-24 3:00 ` John Prevost
2004-10-24 5:18 ` skaller
2004-10-24 22:52 ` Nathaniel Gray
2004-10-25 13:21 ` Damien Doligez
2004-10-25 14:25 ` Jacques Carette
2004-10-26 14:07 ` Damien Doligez
2004-10-26 15:05 ` Jacques Carette
2004-10-26 17:34 ` skaller
2004-10-26 20:02 ` [Caml-list] Combined compilation and linking Jon Harrop
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=aee06c9e04102314495aa44fee@mail.gmail.com \
--to=n8gray@gmail.com \
--cc=caml-list@davidb.org \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--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