caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
To: Yotam Barnoy <yotambarnoy@gmail.com>
Cc: Mark Shinwell <mshinwell@janestreet.com>,
	Alain Frisch <alain.frisch@lexifi.com>,
	 Gerd Stolpmann <info@gerd-stolpmann.de>,
	Pierre Chambart <pierre.chambart@laposte.net>,
	 Markus Mottl <markus.mottl@gmail.com>,
	OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] <DKIM> Re: Status of Flambda in OCaml 4.03
Date: Fri, 11 Mar 2016 16:09:03 +0100	[thread overview]
Message-ID: <CAGrdgiVxTO022c20yN1zD8wg60+Y5ZS7weQO8NKCpvP=GO0P5w@mail.gmail.com> (raw)
In-Reply-To: <CAN6ygOmKvHA1wpSBzA7JnPApRYmLSukOT7kabvqC=dG9hGxjLA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

On Fri, Mar 11, 2016 at 3:48 PM, Yotam Barnoy <yotambarnoy@gmail.com> wrote:

> Another question: how will 4.03 be handled with regard to OPAM? The way I
> see it, the majority of users will want Flambda activated by default.
> Companies or individuals that depend on OCaml for their business will
> probably want to start off with Flambda turned off, and turn it on as
> needed. Additionally, to get Flambda tested by as many people as possible,
> I believe we want people to use it by default.


One of the (many) things I think is done right in OPAM is the `opam switch
...` framework, so you can have multiple compilers installed easily and
handle them on a simple switching framework.

Operationally, I'd put it on an Ocaml 4.03+flambda and then in
point-release .1 or .2 I'd make it the default once it has seen some use by
the early adopters, having an ocaml 4.03+no-flambda option for those who
are behind on schedule. This would allow people to gracefully roll forward
one release, and gracefully roll backward once the switch happens which
lessens the strain on a lot of stuff operationally.

The more risky alternative is to just make flambda the default in 4.03 and
have a no-flambda option for those in the know, but this risks introducing
regressions at a greater extent and should be balanced by the knowledge of
how stable flambda has proven to be. If, for instance, it has seen major
use inside Janes St. for some time and has been generally stable, this is a
far more viable option.



-- 
J.

[-- Attachment #2: Type: text/html, Size: 2031 bytes --]

  reply	other threads:[~2016-03-11 15:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 22:10 [Caml-list] " Markus Mottl
2016-03-08 22:53 ` Alain Frisch
2016-03-09  3:55   ` Markus Mottl
2016-03-09  7:14     ` Mark Shinwell
2016-03-10  0:59       ` Markus Mottl
2016-03-10  1:32         ` Yotam Barnoy
2016-03-10  1:43           ` Markus Mottl
2016-03-10  7:20             ` Mark Shinwell
2016-03-10 15:32               ` Markus Mottl
2016-03-10 15:49                 ` Gabriel Scherer
2016-04-17  8:43                   ` Jesper Louis Andersen
2016-04-17  8:59                     ` Mohamed Iguernlala
2016-04-17 15:43                       ` Markus Mottl
2016-03-10 20:12                 ` [Caml-list] <DKIM> " Pierre Chambart
2016-03-10 21:08                   ` Markus Mottl
2016-03-10 22:51                   ` Gerd Stolpmann
2016-03-11  8:59                     ` Mark Shinwell
2016-03-11  9:05                       ` Mark Shinwell
2016-03-11  9:09                       ` Alain Frisch
2016-03-11  9:26                         ` Mark Shinwell
2016-03-11 14:48                           ` Yotam Barnoy
2016-03-11 15:09                             ` Jesper Louis Andersen [this message]
2016-03-11 16:58                       ` Markus Mottl

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='CAGrdgiVxTO022c20yN1zD8wg60+Y5ZS7weQO8NKCpvP=GO0P5w@mail.gmail.com' \
    --to=jesper.louis.andersen@gmail.com \
    --cc=alain.frisch@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=markus.mottl@gmail.com \
    --cc=mshinwell@janestreet.com \
    --cc=pierre.chambart@laposte.net \
    --cc=yotambarnoy@gmail.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).