caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rich@annexia.org>
To: Alain Frisch <alain@frisch.fr>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Immutable strings
Date: Mon, 14 Jul 2014 18:40:08 +0100	[thread overview]
Message-ID: <20140714174008.GA30965@annexia.org> (raw)
In-Reply-To: <53BD49B1.6000203@frisch.fr>

On Wed, Jul 09, 2014 at 03:54:57PM +0200, Alain Frisch wrote:
> On 07/08/2014 02:24 PM, Gerd Stolpmann wrote:
> >It will create confusion even with actively maintained code bases. What
> >could help here is very clear communication when the change will be the
> >standard behavior, and how the migration will take place.
> 
> It's a very different kind of criticism from your initial point
> about the decision of going into the current direction.  Point
> taken: the development team will need to communicate about the
> expected timeline and migrate path.  But note that 4.02 is not even
> out, and since the default behavior is the previous one, there is no
> hurry, and it's fine if people wait a few months before trying the
> new mode.   It doesn't seem crazy to wait for some early user
> feedback and synchronize with them before deciding on a more precise
> plan for the wider community. For instance, you feedback about
> porting ocamlnet is quite useful and the current discussion shows
> that several solutions compete and need further thought.  Without
> the new compiler switch, this discussion would not have taken place.

The problem we may* have is that we have to support OCaml back to ~
3.10 from the same code base.

Rich.

* I say `may' in that sentence because I've just ignored the warnings
so far -- having much bigger problems with armv7hl & aarch64 support
in 4.02 right now.

-- 
Richard Jones
Red Hat

  parent reply	other threads:[~2014-07-14 17:40 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
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 [this message]
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=20140714174008.GA30965@annexia.org \
    --to=rich@annexia.org \
    --cc=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).