From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] OCaml release 4.11.1
Date: Tue, 1 Sep 2020 16:42:22 +0200 [thread overview]
Message-ID: <645ee64e-5ce8-a582-c689-d57338d3be27@inria.fr> (raw)
In-Reply-To: <e9e7fc73-943a-b6e4-7e98-07e30078c7d4@inria.fr>
Dear OCaml users,
A serious bug has been discovered last week in OCaml 4.11.0:
explicit polymorphic annotations are checked too permissively.
Some incorrect programs (possibly segfaulting) are accepted
by the compiler in 4.11.0.
Programs accepted by OCaml 4.10 are unchanged.
We are thus releasing OCaml 4.11.1 as an early bugfix version.
You are advised to upgrade to this new version if you were
using OCaml 4.11.0.
It is (or soon will be) available as a set of OPAM switches with
opam switch create 4.11.1
and as a source download here:
https://caml.inria.fr/pub/distrib/ocaml-4.11/
This bug was introduced when making polymorphic recursion
easier to use. We are working on making the typechecker
more robust and more exhaustively tested to avoid such
issues in the future.
Happy hacking,
-- Florian Angeletti for the OCaml team.
### Bug fixes:
- #9856, #9857: Prevent polymorphic type annotations from generalizing
weak polymorphic variables.
(Leo White, report by Thierry Martinez, review by Jacques Garrigue)
- #9859, #9862: Remove an erroneous assertion when inferred function types
appear in the right hand side of an explicit :> coercion
(Florian Angeletti, report by Jerry James, review by Thomas Refis)
prev parent reply other threads:[~2020-09-01 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 16:10 [Caml-list] OCaml release 4.11.0 Florian Angeletti
2020-09-01 14:42 ` Florian Angeletti [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=645ee64e-5ce8-a582-c689-d57338d3be27@inria.fr \
--to=florian.angeletti@inria.fr \
--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).