From: "Loup Vaillant" <loup.vaillant@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Not really a bug but...
Date: Sat, 16 Jun 2007 12:10:35 +0200 [thread overview]
Message-ID: <6f9f8f4a0706160310m285f0b63r7e2087a31ae46671@mail.gmail.com> (raw)
In-Reply-To: <46739188.5060605@inria.fr>
2007/6/16, Alain Frisch <Alain.Frisch@inria.fr>:
> Jon Harrop wrote:
> > Any chance of changing the semantics of string literals so they aren't static?
> [...]
> If it were done automatically, there would be a penalty for
> the common case of immutable strings; to avoid it, you'd need to lift
> constant literals out of abstractions, which is not very nice.
By the way, why Ocaml didn't take the Java path, i.e. making truly
immutable strings, And provide mutable string buffers as well? Any
chance of seing someone exploring that path? (Some usefull features
would then be fast consing and catenation, and some easier string
sharing).
Loup
next prev parent reply other threads:[~2007-06-16 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 0:17 Jon Harrop
2007-06-16 7:30 ` [Caml-list] " Alain Frisch
2007-06-16 10:02 ` Christophe TROESTLER
2007-06-16 10:10 ` Loup Vaillant [this message]
2007-06-16 15:59 ` Richard Jones
2007-06-16 17:01 ` skaller
2007-06-16 17:03 ` Jon Harrop
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=6f9f8f4a0706160310m285f0b63r7e2087a31ae46671@mail.gmail.com \
--to=loup.vaillant@gmail.com \
--cc=caml-list@yquem.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).