From: j h woodyatt <jhw@conjury.org>
To: The Caml Trade <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: immutable strings (Re: Array 4 MB size limit)
Date: Thu, 25 May 2006 00:23:51 -0700 [thread overview]
Message-ID: <77959C0C-D878-412A-A1A3-3C9D382EDB93@conjury.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0605242225320.5602@droopy>
On May 24, 2006, at 10:56 PM, Martin Jambon wrote:
>
> So I'd really love to see actual examples where using immutable
> strings would be such an improvement over mutable strings.
> If the problem is just to ensure that string data won't be changed
> by the user of a library, then it is trivial using module
> signatures and String.copy for the conversions.
I have no dog in this fight, but I can imagine a pragmatic approach
that might satisfy some of these concerns without introducing much in
the way of extra runtime complexity costs.
Change the way strings are boxed so that there is an additional tag
for immutable strings as opposed to the normal mutable ones. In all
respects, allow string objects with either tag to be treated the same
by functions that do not modify the content of the string. When the
"safe" variants of the string mutation functions are called on a
string object with the immutable tag, throw a runtime exception.
Finally, provide a function that changes the tag of a string from
mutable to immutable, i.e. like a special blessed case of
Obj.set_tag. Not from immutable to mutable, though-- that should be
disallowed. If the -unsafe is not set, then allow a new compiler
option -constliteral (or something) that would make all string
literals immutable. You'd need to use String.copy to get a mutable
string with contents copied from an immutable one.
Of course, I can't offer a convincing reason to believe this would
bring an improvement over what we have today. My proposal would not
give the programmer any assurance that contents of string values
passed as parameters to library functions are not modified by the
library, i.e. the "unsafe" functions would still work. It *might*
give a pragmatic benefit of surfacing unintentional programming
errors earlier than they might otherwise be found, but I'm not
prepared to argue in defense of that.
If you did immutable strings this way, it would be nice for the sake
of consistency to have a comparable feature for arrays.
—
j h woodyatt <jhw@conjury.org>
next prev parent reply other threads:[~2006-05-25 7:24 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 18:12 Array 4 MB size limit akalin
2006-05-15 18:22 ` [Caml-list] " Nicolas Cannasse
2006-05-15 20:32 ` Damien Doligez
2006-05-15 21:27 ` akalin
2006-05-15 22:51 ` Oliver Bandel
2006-05-16 0:48 ` Brian Hurt
2006-05-16 9:57 ` Damien Doligez
2006-05-16 15:10 ` Markus Mottl
2006-05-16 8:01 ` Xavier Leroy
2006-05-16 8:20 ` Nicolas Cannasse
2006-05-19 17:13 ` Xavier Leroy
2006-05-19 5:57 ` Frederick Akalin
2006-05-19 6:21 ` Oliver Bandel
2006-05-19 12:15 ` Jon Harrop
2006-05-19 19:36 ` akalin
2006-05-19 20:17 ` Oliver Bandel
2006-05-19 16:28 ` Jozef Kosoru
2006-05-19 20:08 ` Oliver Bandel
2006-05-19 21:26 ` Jon Harrop
2006-05-20 1:06 ` Brian Hurt
2006-05-20 18:32 ` brogoff
2006-05-20 21:29 ` immutable strings II ([Caml-list] Array 4 MB size limit) Oliver Bandel
2006-05-22 22:09 ` Aleksey Nogin
2006-05-20 21:11 ` immutable strings (Re: [Caml-list] " Oliver Bandel
2006-05-25 4:32 ` immutable strings (Re: " Stefan Monnier
2006-05-25 5:56 ` [Caml-list] " Martin Jambon
2006-05-25 7:23 ` j h woodyatt [this message]
2006-05-25 10:22 ` Jon Harrop
2006-05-25 19:28 ` Oliver Bandel
2006-05-25 11:14 ` Brian Hurt
2006-05-25 19:42 ` Oliver Bandel
2006-05-26 6:51 ` Alain Frisch
2006-05-25 17:31 ` Aleksey Nogin
2006-05-25 19:54 ` Martin Jambon
2006-05-25 11:18 ` Brian Hurt
2006-05-25 17:34 ` Aleksey Nogin
2006-05-25 18:44 ` Tom
2006-05-25 23:00 ` Jon Harrop
2006-05-25 23:15 ` Martin Jambon
2006-05-20 0:57 ` [Caml-list] Array 4 MB size limit Brian Hurt
2006-05-20 1:17 ` Frederick Akalin
2006-05-20 1:52 ` Brian Hurt
2006-05-20 9:08 ` Jozef Kosoru
2006-05-20 10:12 ` skaller
2006-05-20 11:06 ` Jozef Kosoru
2006-05-20 12:02 ` skaller
2006-05-20 21:42 ` Oliver Bandel
2006-05-21 1:24 ` skaller
2006-05-21 14:10 ` Oliver Bandel
[not found] ` <Pine.LNX.4.63.0605200847530.10710@localhost.localdomain>
2006-05-20 19:52 ` Jozef Kosoru
2006-05-20 21:45 ` Oliver Bandel
2006-05-21 9:26 ` Richard Jones
[not found] ` <5CE30707-5DCE-4A22-970E-A49C36F9C901@akalin.cx>
2006-05-22 10:40 ` Richard Jones
2006-05-20 10:51 ` Jozef Kosoru
2006-05-20 14:22 ` Brian Hurt
2006-05-20 18:41 ` j h woodyatt
2006-05-20 19:37 ` Jon Harrop
2006-05-20 20:47 ` Jozef Kosoru
2006-05-26 18:34 ` Ken Rose
2006-05-20 22:07 ` Oliver Bandel
2006-05-20 15:15 ` Don Syme
2006-05-20 22:15 ` Oliver Bandel
2006-05-21 1:25 ` skaller
2006-05-28 23:20 [Caml-list] Re: immutable strings (Re: Array 4 MB size limit) Harrison, John R
2006-05-29 2:36 ` Martin Jambon
2006-05-31 12:53 ` Jean-Christophe Filliatre
2006-05-29 20:52 Harrison, John R
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=77959C0C-D878-412A-A1A3-3C9D382EDB93@conjury.org \
--to=jhw@conjury.org \
--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