caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] OCaml 4.06.0+rc1
Date: Sun, 29 Oct 2017 12:49:00 +0100	[thread overview]
Message-ID: <CAPFanBFyc0aZNXY9mwP5Bv71YLt+hsCPUZTCbSO_XhFJA6+Q=w@mail.gmail.com> (raw)

Dear OCaml users,

We have created a first release candidate of the upcoming
OCaml 4.06.0 release for your repeated testing pleasure. It is
available as opam switches 4.06.0.+rc1 (or +rc1+flambda, etc.)

  opam switch 4.06.0+rc1

or as source archives at

  http://caml.inria.fr/pub/distrib/ocaml-4.06/

The Changelog since 4.05.0 is available at

  http://caml.inria.fr/pub/distrib/ocaml-4.06/notes/Changes.4.06.0+rc1.txt

The more specific list of changes since 4.06.0+beta2 is
included at the end of this email.

We are hoping to make the actual 4.06.0 release shortly. If
you are the maintainer of a publicly-distributed OCaml
package, now is the time to make sure you have made
a 4.06-ready release.

Happy hacking,

-- Gabriel Scherer for the OCaml team.


Changes since beta2:

* MPR#7598, GPR#1402: the magic numbers used by the OCaml
  compiler (versioning numbers for object files and the binary
  AST format) have been updated, which means that some tools
  may have to be updated to the 4.06-specific magic numbers,
  even if they appeared to work fine in
  4.06.0+beta2. (Apologies updating so late in the release
  cycle.)
  (Damien Doligez, review by Alain Frisch, Xavier Leroy and Sébastien Hinderer,
  report by Bart Jacobs)

- GPR#594: New manual chapter on polymorphism troubles: weakly
  polymorphic types, polymorphic recursion,and higher-ranked
  polymorphism.
  (Florian Angeletti, review by Damien Doligez, Gabriel Scherer,
   and Gerd Stolpmann)

  You can preview this chapter (and the whole 4.06.0 manual) at:
    http://www.polychoron.fr/ocaml-beta-manual/4.06+rc1/polymorphism.html

- GPR#1409: Fix to enable NetBSD/powerpc to work.
  (Håvard Eidnes)

- MPR#7657, GPR#1424: ensures correct call-by-value semantics
  when eta-expanding functions to eliminate optional arguments
  (Alain Frisch, report by sliquister, review by Leo White and Jacques
  Garrigue)

- GPR#1457, ocamldoc: restore label for exception in the latex
  backend (omitted since 4.04.0)
  (Florian Angeletti, review by Gabriel Scherer)

- MPR#6329, GPR#1437: Introduce padding word before "data_end"
  symbols to ensure page table tests work correctly on an
  immediately preceding block of zero size.
  (Mark Shinwell, review by Xavier Leroy)

- MPR#7658, GPR#1439: Fix Spacetime runtime system compilation
  with -force-safe-string
  (Mark Shinwell, report by Christoph Spiel, review by Gabriel Scherer)

- GPR#1407: Fix raw_spacetime_lib
  (Leo White, review by Gabriel Scherer and Damien Doligez)

             reply	other threads:[~2017-10-29 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 11:49 Gabriel Scherer [this message]
2017-10-30 18:25 ` David Allsopp
     [not found]   ` <09738422-5ADF-43DE-856A-2727515BD2FA@acm.org>
2017-11-02 11:59     ` David Allsopp
2017-11-03 10:53 ` [Caml-list] Upcoming breaking changes in Ocamldoc 4.06 octachron

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='CAPFanBFyc0aZNXY9mwP5Bv71YLt+hsCPUZTCbSO_XhFJA6+Q=w@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).