From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Unboxed float tuples
Date: Sun, 8 Nov 2009 16:46:09 +0000 [thread overview]
Message-ID: <200911081646.09963.jon@ffconsultancy.com> (raw)
In-Reply-To: <91a3da520911080801w6637b652w94a717a830b1c5bd@mail.gmail.com>
On Sunday 08 November 2009 16:01:48 Daniel Bünzli wrote:
> Using tuples (vs records) to handles points and vectors is
> syntactically more lightweight (IMHO).
If you want to handle structs and vectors then you probably want structs
(value types) and not boxed representations like tuples and records anyway.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2009-11-08 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 16:01 Daniel Bünzli
2009-11-08 16:46 ` Jon Harrop [this message]
2009-11-08 17:29 ` [Caml-list] " Martin Jambon
2009-11-08 19:39 ` Brian Hurt
2009-11-08 20:36 ` Jon Harrop
2009-11-08 20:09 ` Richard Jones
2009-11-08 20:58 ` Christophe Raffalli
2009-11-08 21:25 ` Lukasz Stafiniak
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=200911081646.09963.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).