caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: Jonas Jensen <jj@issuu.com>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml release roadmap
Date: Thu, 14 May 2015 23:20:38 +0200	[thread overview]
Message-ID: <CAPFanBG35+bcVHrGoyCyM=gGe5qn+fMLyF0dbr+5eubUYkUUcQ@mail.gmail.com> (raw)
In-Reply-To: <CALGm1VhGaJUC8a0Hkuvcv3627_z7LgLhJ+BDXNU3nbYfncUwzw@mail.gmail.com>

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

Note that the readability benefits of inline records on value-manipulating
code can already be reaped by just using variant constructors with only one
argument, a record. The feature is more of an optimization of the memory
representation of this case (won't matter much for most applications) --
and also, admittedly, the readability of the type declaration. Its future
availability could be taken as a mere encouragement to use this style
already today.

On Thu, May 14, 2015 at 10:51 PM, Damien Doligez <damien.doligez@inria.fr>
wrote:

> On Wed, May 13, 2015 at 9:20 AM, Jonas Jensen <jj@issuu.com> wrote:
>
> > Is there a good reason not to release current trunk as 4.03 soon?
>
> Manpower is one such reason. Also, we like to thoroughly test our
> code before we release it. And there are several important features
> in the works.
>
> > According to http://caml.inria.fr/mantis/view.php?id=5528, the "Inline
> > records for constructor arguments" feature has been merged to trunk. I
> > think this is a huge improvement to the language that will improve
> > code readability for at lot of projects.
>
> I see it as a rather small feature. It's not in the same league as GADTs
> or Modular Implicits, for example.
>
> > An end-of-year release seems
> > very far away, especially if the release date slips because multicore
> > support is such a disruptive change.
>
> I know our release schedule is rather slow, but OCaml is a really
> complex system and we like to think things through before we
> release, and this has already saved us from several bad design
> decisions.
>
> -- Damien
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

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

      reply	other threads:[~2015-05-14 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:24 Damien Doligez
2015-05-11 11:46 ` Francois Berenger
2015-05-11 13:31   ` Mark Shinwell
2015-05-11 13:31     ` Mark Shinwell
2015-05-26 17:13     ` Richard W.M. Jones
2015-06-04 20:34       ` Damien Doligez
2015-05-13 13:20 ` Jonas Jensen
2015-05-14 20:51   ` Damien Doligez
2015-05-14 21:20     ` Gabriel Scherer [this message]

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='CAPFanBG35+bcVHrGoyCyM=gGe5qn+fMLyF0dbr+5eubUYkUUcQ@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=jj@issuu.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).