From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] OCaml 4.11.0, first beta release
Date: Mon, 29 Jun 2020 17:25:41 +0200 [thread overview]
Message-ID: <c3b58aec-fc46-4e32-5a67-8daf66dfc2e5@inria.fr> (raw)
In-Reply-To: <800d1d00-1fb8-1485-3022-c581753b3fba@inria.fr>
Dear OCaml users,
The release of OCaml 4.11.0 is approaching.
After three alpha releases, we have created a first beta version to help you
adapt your software to the new features ahead of the release.
The compatibility of the opam ecosystem with OCaml 4.11.0 is currently quite
good, and it should be possible to test this beta without too much trouble.
The source code is available at these addresses:
https://github.com/ocaml/ocaml/archive/4.11.0+beta1.tar.gz
https://caml.inria.fr/pub/distrib/ocaml-4.11/ocaml-4.11.0+beta1.tar.gz
The compiler can also be installed as an OPAM switch with one of the
following commands.
opam switch create ocaml-variants.4.11.0+beta1
--repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
or
opam switch create ocaml-variants.4.11.0+beta1+<VARIANT>
--repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
where you replace <VARIANT> with one of these:
afl
flambda
fp
fp+flambda
We want to know about all bugs. Please report them here:
https://github.com/ocaml/ocaml/issues
If you are interested by the list of new features, and the on-going list
of bug fixes the
updated change log for OCaml 4.11.0 is available at:
https://github.com/ocaml/ocaml/blob/4.11/Changes
Compared to the last alpha release, this first beta release contains the
following new bug fixes:
Driver
- #9011: Allow linking .cmxa files with no units on MSVC by not
requiring the
.lib file to be present.
(David Allsopp, report by Dimitry Bely, review by Xavier Leroy)
Typechecker
- #9384, #9385: Fix copy scope bugs in substitutions
(Leo White, review by Thomas Refis, report by Nick Roberts)
- #9695, #9702: no error when opening an alias to a missing module
(Jacques Garrigue, report and review by Gabriel Scherer)
Warnings
- #7897, #9537: Fix warning 38 for rebound extension constructors
(Leo White, review by Florian Angeletti)
- #9244: Fix some missing usage warnings
(Leo White, review by Florian Angeletti)
Toplevels
- #9415: Treat `open struct` as `include struct` in toplevel
(Leo White, review by Thomas Refis)
- #9416: Avoid warning 58 in flambda ocamlnat
(Leo White, review by Florian Angeletti)
Flambda backend
- #9163: Treat loops properly in un_anf
(Leo White, review by Mark Shinwell, Pierre Chambart and Vincent
Laviron)
Happy hacking,
-- Florian Angeletti for the OCaml team.
prev parent reply other threads:[~2020-06-29 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:15 [Caml-list] OCaml 4.11.0, first alpha release Florian Angeletti
2020-06-04 7:29 ` [Caml-list] OCaml 4.11.0, second " Florian Angeletti
2020-06-17 15:42 ` [Caml-list] OCaml 4.11.0, third " Florian Angeletti
2020-06-18 1:53 ` [Caml-list] 300$ Bounty for the feature compilation cache in opam Francois Berenger
2020-06-18 9:00 ` Fabrice Le Fessant
2020-06-18 9:09 ` Louis Roché
2020-06-18 9:22 ` Gabriel Scherer
2020-06-18 11:18 ` Muriel SHAN SEI FAN
2020-06-29 15:25 ` 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=c3b58aec-fc46-4e32-5a67-8daf66dfc2e5@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).