From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: John Prevost <j.prevost@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] What's the current status of int32 and int64 boxing?
Date: Wed, 14 Jul 2004 11:43:16 +0200 [thread overview]
Message-ID: <20040714094316.GA24083@yquem.inria.fr> (raw)
In-Reply-To: <d849ad2a040713201751dc587d@mail.gmail.com>
> I was just wondering what exactly to expect for performance with int32
> and int64 types in records and arrays right now. Browsing through the
> archives, I got the feeling that these types currently appear unboxed
> in record types, but boxed in array types. Is that still correct?
No: int32 and int64 are always boxed in records and arrays. Only
"big arrays" (the Bigarray library) support unboxed int32 and int64
elements.
- Xavier Leroy
-------------------
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
prev parent reply other threads:[~2004-07-14 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 3:17 John Prevost
2004-07-14 9:43 ` Xavier Leroy [this message]
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=20040714094316.GA24083@yquem.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=j.prevost@gmail.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