From: Edgar Friendly <thelema314@gmail.com>
To: Christopher L Conway <cconway@cs.nyu.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Immutable cyclic data structures via a
Date: Sat, 13 Dec 2008 19:47:46 -0600 [thread overview]
Message-ID: <494465C2.2000807@gmail.com> (raw)
In-Reply-To: <loom.20081213T213803-424@post.gmane.org>
Christopher L Conway wrote:
> This makes me wonder: if you add mutable fields to a type in order to
> build a cyclic data structure, but you intend to use the data
> structure immutably once it is built, is there any way to "freeze" the
> value, producing an immutable cyclic structure? This is a common
> pattern, similar to Bloch's Builder pattern for Java.[1]
>
> You might have an operation, call it "unmute", that changes the type
> of the structure. There would need to be a corresponding type-level
> operation, call it "UNMUTE", that strips the "mutable" qualifier from
> mutable fields. E.g.,
<SNIP>
> I'm pretty confident this isn't possible in plain-vanilla OCaml. You
> can do something similar (at a high cost in ugliness) using a
> variation of "Tying the Knot" a la Haskell.[2]
ExtLib (and thus batteries) uses your unmute (called [inj]) for
converting a mutable list into the normal immutable list. The definition:
external inj : 'a mut_list -> 'a list = "%identity"
It's effectively using Obj.magic, but specialized on these types.
As always, be *very* careful when using this kind of type system voodoo,
but it can work under certain circumstances.
E.
next prev parent reply other threads:[~2008-12-14 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 21:45 Christopher L Conway
2008-12-13 23:30 ` [Caml-list] " Jeremy Yallop
2008-12-13 23:43 ` Jeremy Yallop
2008-12-14 1:47 ` Edgar Friendly [this message]
2008-12-14 9:10 ` Francois Pottier
2008-12-14 14:29 ` blue storm
2008-12-14 20:06 ` Richard Jones
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=494465C2.2000807@gmail.com \
--to=thelema314@gmail.com \
--cc=caml-list@inria.fr \
--cc=cconway@cs.nyu.edu \
/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