From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] First release candidate for OCaml 5.3.0
Date: Thu, 19 Dec 2024 13:28:46 +0100 (CET) [thread overview]
Message-ID: <1760648701.4109150.1734611326044.JavaMail.zimbra@inria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 2917 bytes --]
Dear OCaml users,
The release of OCaml 5.3.0 is imminent.
As a final step, we are publishing a release candidate to check that everything
is in order before the release in the upcoming week(s).
If you find any bugs, please report them on the OCaml's issue
tracker ( [ https://github.com/ocaml/ocaml/issues | https://github.com/ocaml/ocaml/issues ] ).
Compared to the second beta, this release candidate contains a regression fix in
the type system (some type expressions were not generalized when they ought to
be), one fix for the new check for dependency order at link time, and an
improvement of the reference manual.
The full change log for OCaml 5.3.0 is available on
GitHub(https://github.com/ocaml/ocaml/blob/5.3/Changes).
A short summary of the changes since the second beta release is also available
below.
Happy hacking,
Florian Angeletti for the OCaml team.
Installation instructions
--------------------------------
The base compiler can be installed as an opam switch with the following commands on opam 2.1 and later:
opam update
opam switch create 5.3.0~rc1
The source code for the release candidate is also directly available on:
* GitHub: https://github.com/ocaml/ocaml/archive/5.3.0-rc1.tar.gz
* OCaml archives at Inria: https://caml.inria.fr/pub/distrib/ocaml-5.3/ocaml-5.3.0~rc1.tar.gz
Fine-tuned compiler configuration
---------------------------------------------
If you want to tweak the configuration of the compiler, you can switch to the option variant with:
opam update
opam switch create <switch_name> ocaml-variants.5.3.0~rc1+options <option_list>
where `<option_list>` is a space-separated list of `ocaml-option-*` packages. For instance, for a `flambda` and `no-flat-float-array` switch:
opam switch create 5.3.0~rc1+flambda+nffa ocaml-variants.5.3.0~rc1+options ocaml-option-flambda ocaml-option-no-flat-float-array
All available options can be listed with `opam search ocaml-option`.
Changes since the second beta
-----------------------------------------
## Type system
- [#13690](https://github.com/ocaml/ocaml/issues/13690): some type expressions were incorrectly not generalized (because they
were assigned to the wrong level pool)
## Compiler user-interface and warnings:
- [#12084](https://github.com/ocaml/ocaml/issues/12084), +[#13669](https://github.com/ocaml/ocaml/issues/13669), +[#13673](https://github.com/ocaml/ocaml/issues/13673):
Check link order when creating archive and when using ocamlopt.
## Documentation
- [#13666](https://github.com/ocaml/ocaml/issues/13666): Rewrite parts of the example code around nested lists in Chapter 6
(Polymorphism and its limitations -> Polymorphic recursion) giving the
"depth" function [in the non-polymorphically-recursive part of the example]
a much more sensible behavior; also fix a typo and some formatting.
(Frank Steffahn, review by Florian Angeletti)
[-- Attachment #2: Type: text/html, Size: 3555 bytes --]
reply other threads:[~2024-12-19 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1760648701.4109150.1734611326044.JavaMail.zimbra@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