caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "John F. Carr" <jfc@MIT.EDU>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Immutable strings
Date: Tue, 29 Jul 2014 07:48:54 -0400	[thread overview]
Message-ID: <21463.35366.495887.430955@gargle.gargle.HOWL> (raw)
In-Reply-To: <CACLX4jQx=06KPK14PbMvQDOd8qams1w_kCYKd=6KVkDvJu6HjA@mail.gmail.com>


 > This isn't my idea, but it seems worth repeating: perhaps it would
 > make sense to have an unmovable byte-array type that had the same
 > memory representation as Bytes.t, with the extra guarantee that the
 > collector wouldn't move it.

I don't think this can be implemented without a significant runtime
change.  If your program is special enough to need pinned strings, try
turning off compaction with Gc.set.  The collector will never move
objects larger than 256 words.

It is easy to allocate a string from outside the heap, so the
collector can not move it, but then you have to do manual memory
management.  Manual memory management means explicit free or a
finalizer on an object you know will outlive any reference to the
string.


  parent reply	other threads:[~2014-07-29 11:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 19:18 Gerd Stolpmann
2014-07-04 20:31 ` Anthony Tavener
2014-07-04 20:38   ` Malcolm Matalka
2014-07-04 23:44   ` Daniel Bünzli
2014-07-05 11:04   ` Gerd Stolpmann
2014-07-16 11:38     ` Damien Doligez
2014-07-04 21:01 ` Markus Mottl
2014-07-05 11:24   ` Gerd Stolpmann
2014-07-08 13:23     ` Jacques Garrigue
2014-07-08 13:37       ` Alain Frisch
2014-07-08 14:04         ` Jacques Garrigue
2014-07-28 11:14   ` Goswin von Brederlow
2014-07-28 15:51     ` Markus Mottl
2014-07-29  2:54       ` Yaron Minsky
2014-07-29  9:46         ` Goswin von Brederlow
2014-07-29 11:48         ` John F. Carr [this message]
2014-07-07 12:42 ` Alain Frisch
2014-07-08 12:24   ` Gerd Stolpmann
2014-07-09 13:54     ` Alain Frisch
2014-07-09 18:04       ` Gerd Stolpmann
2014-07-10  6:41         ` Nicolas Boulay
2014-07-14 17:40       ` Richard W.M. Jones
2014-07-08 18:15 ` mattiasw
2014-07-08 19:24   ` Daniel Bünzli
2014-07-08 19:27     ` Raoul Duke
2014-07-09 14:15   ` Daniel Bünzli
2014-07-14 17:45   ` Richard W.M. Jones
2014-07-21 15:06 ` Alain Frisch
     [not found]   ` <20140722.235104.405798419265248505.Christophe.Troestler@umons.ac.be>
2014-08-29 16:30     ` Damien Doligez

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=21463.35366.495887.430955@gargle.gargle.HOWL \
    --to=jfc@mit.edu \
    --cc=caml-list@inria.fr \
    --cc=yminsky@janestreet.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;
as well as URLs for NNTP newsgroup(s).