From: "Jakob Lichtenberg" <jl@itu.dk>
To: <caml-list@inria.fr>
Subject: [Caml-list] ocaml internal representation
Date: Thu, 13 Mar 2003 06:32:10 -0800 [thread overview]
Message-ID: <003e01c2e96d$5557a6f0$6401a8c0@redmond.corp.microsoft.com> (raw)
In O'Caml the types are compiled away, right?
Then, is there actually a performance/memory overhead in replacing:
type coord = int * int
with:
type coord = Coord of (int * int)
Is it recognized as a 'reasonable' way to get the type system to help me not
mixing up stuff (except for signatures of course)?
Slightly more general: Did I miss any doc. about this in the O'Caml manual?
Thanks,
- Jakob Lichtenberg
--
Jakob Lichtenberg - jl@itu.dk - http://www.itu.dk/people/jl/
-------------------
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 reply other threads:[~2003-03-13 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 14:32 Jakob Lichtenberg [this message]
2003-03-13 16:45 ` Xavier Leroy
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='003e01c2e96d$5557a6f0$6401a8c0@redmond.corp.microsoft.com' \
--to=jl@itu.dk \
--cc=caml-list@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).