From: Goswin von Brederlow <goswin-v-b@web.de>
To: caml-list@inria.fr
Subject: [Caml-list] A shallow option type
Date: Sat, 05 May 2012 15:33:58 +0200 [thread overview]
Message-ID: <87r4uykb09.fsf@frosties.localnet> (raw)
Hi,
I wish there was an option type that would work without extra
indirection (or more importantly without extra allocation of an ocaml
value when setting it to something).
Why? I'm interfacing with C in a multithreaded way. The data is
allocated on the C side so it won't be moved around by the GC. The ocaml
side will modify data and the C side will utilize it. Now if ocaml
changes a multable 'a option then it will allocate a block for "Some x"
and the GC will move that block around during compaction. Which means
the 'a option can't be safely used without holding the runtime system
lock. Which then means the threads can't run in parallel.
What I want is a
type 'a shallow = NULL | 'a (constraint 'a != 'b shallow)
I have some ideas on how to implement this in a module as abstract type
providing get/set/clear functions, which basically means I map None to a
C NULL pointer and Some x to plain x. I know x can never be the NULL
pointer, except when someone creates a 'a shallow shallow and sets Some
None. That would turn into simply None.
Is it possible to somehow declare the constraint that 'a in 'a shallow must
not be itself a 'b shallow?
MfG
Goswin
next reply other threads:[~2012-05-05 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 13:33 Goswin von Brederlow [this message]
2012-05-05 13:50 ` Gabriel Scherer
2012-05-05 14:48 ` Andreas Rossberg
2012-05-05 15:07 ` Andreas Rossberg
2012-05-05 16:22 ` Goswin von Brederlow
2012-05-05 17:11 ` Gabriel Scherer
2012-05-06 10:12 ` Goswin von Brederlow
2012-05-06 10:20 ` Goswin von Brederlow
2012-05-06 13:01 ` Jacques Garrigue
2012-05-06 15:34 ` Goswin von Brederlow
2012-05-07 0:29 ` Jacques Garrigue
2012-05-07 1:27 ` Jacques Garrigue
2012-05-07 2:34 ` Jacques Garrigue
2012-05-07 8:11 ` Jacques Garrigue
2012-05-07 17:07 ` Goswin von Brederlow
2012-05-08 0:07 ` Jacques Garrigue
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=87r4uykb09.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--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).