Read the latest releases and updates from the OCaml compiler, OCaml infrastructure and the OCaml Platform Tools.
The Dune Team is happy to announce the release of Dune 3.18.2.
This release contains a bug fix to fix a compatibility issue with ocaml.5.4.0.
ocaml.5.4.0 by avoiding shadowing sigwinch (@nojb,
#11639)The Dune Team is happy to announce the release of Dune 3.18.1!
This release contains a bug fix for pkg-config that prevents it from finding some
libraries in specific contexts.
--personality flag would result in pkgconf not finding libraries in some
contexts. (#11619, @MisterDA)The Dune Team is happy to announce the release of Dune 3.18.0!
This release contains changes to support the new x-maintenance-intent field
by default. It also contains some changes regarding the cache about how it
handles file permissions. It introduces a new (format-dune-file ...) stanza
with the intention to formalize the dune format-dune-file command as an inside
rule. Finally, it includes various bug fixes for Dune.
Support HaikuOS: don't call execve since it's not allowed if other pthreads
have been created. The fact that Haiku can't call execve from other threads
than the principal thread of a process (a team in haiku jargon), is a
discrepancy to POSIX and hence there is a bug about
it. (@Sylvain78, #10953)
Fix flag ordering in generated Merlin configurations (#11503, @voodoos, fixes ocaml/merlin#1900, reported by @vouillon)
Add (format-dune-file <src> <dst>) action. It provides a replacement to
dune format-dune-file command. (#11166, @nojb)
Allow the --prefix flag when configuring dune with ocaml configure.ml.
This allows to set the prefix just like $ dune install --prefix. (#11172,
@rgrinberg)
Allow arguments starting with + in preprocessing definitions (starting with
(lang dune 3.18)). (@amonteiro, #11234)
Support for opam (maintenance_intent ...) in dune-project (#11274, @art-w)
Validate opam maintenance_intent (#11308, @art-w)
Support not in package dependencies constraints (#11404, @art-w, reported
by @hannesm)
Warn when failing to discover root due to reads failing. The previous behavior was to abort. (@KoviRobi, #11173)
Use shorter path for inline-tests artifacts. (@hhugo, #11307)
Allow dash in dune init project name (#11402, @art-w, reported by @saroupille)
On Windows, under heavy load, file delete operations can sometimes fail due to AV programs, etc. Guard against it by retrying the operation up to 30x with a 1s waiting gap (#11437, fixes #11425, @MSoegtropIMC)
Cache: we now only store the executable permission bit for files (#11541, fixes #11533, @ElectreAAS)
Display negative error codes on Windows in hex which is the more customary
way to display NTSTATUS codes (#11504, @MisterDA)
We are delighted to announce the release of Odoc 3! This is a big release with loads of new features and bug fixes, and we encourage everyone to install it and try the new features!
This release has been cooking for a long time - it’s been more than a year since odoc 2.4 landed, and a huge amount of work has gone into this. Thanks to the many others who contributed, either by code or by comments: @juloo, @panglesd, @EmileTrotignon, @gpetiot, @trefis, @sabine, @dbuenzli, @yawaramin, and more.
Here is an overview of some major new features:
With this release we’re including a driver that makes use of all the exciting new features of odoc. This driver has been used to create the docs site for the various odoc tools. However, Dune does not yet support odoc 3 since the Dune rules for running odoc via Dune need to be rewritten to reflect the odoc's new CLI and the new incremental build related capabilities odoc 3 brings.
Until Dune supports odoc 3, here is how to get started:
$ opam install odoc-driver # will install odoc 3
$ odoc_driver odoc odoc-parser odoc-driver odoc-md sherlodoc --remap
and point your browser at _html/index.html. This example shows odoc_driver creating the docs for exactly the 5 packages specified. While doing so, it will remap links to other packages to instead link to their documentation page hosted on ocaml.org (see "Remapping dependencies" in the odoc documentation).
If you try the above command, you'll note something interesting, and hopefully this will encourage you to run odoc_driver on your own packages before you release them, as then you'll be able to avoid slightly embarrassing post-release fixes like this one 😬
odoc html-fragment not producing headings correctly by jonludlam · Pull Request #1306 · ocaml/odoc · GitHubWe are happy to announce the release of ppxlib.0.36.0!
With this release, the internal AST that ppxlib targets has been bumped to the AST of OCaml 5.2. Ppx authors can now use features from OCaml 5.2. Ppxlib still supports any OCaml compiler after and including 4.08.0.
Many ppxes will be broken by changes made to the representation of functions. Authors are encouraged to read the upgrade guide.
Change Location.none to match the compiler's Location.none as of OCaml
4.08. This fixes a bug in loc_of_attribute (#540, @ncik-roberts, @patricoferris)
Bump ppxlib's AST to 5.2.0 (#514, @patricoferris)
Add the [@@@expand_inline] transformation and support for floating attribute context
free transformations. (#560, @jaymody)
Add a -raise-embedded-errors flag to the driver. Setting this flag raises the first
ocaml.error embedded in the final AST.
Export Ast_pattern.fail. (#563, @ceastlund)
Make Ast_traverse.sexp_of more concise, and add a test. (#561, @ceastlund)
We are happy to announce the release of ppxlib.0.35.0!
The main feature of this release is improved support for OCaml 5.3, allowing ppx users to have ppx rewriters operate on files with the new effect syntax.
Note that ppx-es and the effect syntax can cohabit but it is possible that ppx rewriters will error out if they encounter effect syntax node in their extension's payload or in the items they generate code from.
This feature also comes with a new --use-compiler-pp driver flag. This flag is required to preserve the effect syntax when the ppxlib driver outputs source code instead of marshalled AST. Note that the vast majority of users won't need to use this flag but it can come in handy in some more advanced use cases.
Allow use of effect syntax in preprocessed files without causing migration failures. (#552, @hhugo, @NathanReb)
Remove support for compilers older than 4.08 (#556, @NathanReb)
Add a --use-compiler-pp flag to the standalone driver. This flag
can be set when the driver outputs source code to make it use the compiler's
Pprintast instead of ppxlib's.
(#555, @NathanReb)
Dune-release 2.1.0 has been released!
With this update,
dune-release delegate-info version has been added, which
shows the current version of the package, as inferred by dune-release.dev-repo field in the .opam file can now be overridden using the --dev-repo
flag on the commands dune-release and dune-release publish.dune-release no longer publishes docs to github pages. This choice has been made
because, as a consequence of publishing to opam-repository, the package
documentation is built and served by ocaml.org/packages.dune-release now works with the experimental package management
feature from Dune Developer Preview.dune-release delegate-info version to show the current version as infered
by the tool (#495, @samoht)--dev-repo to dune-release and dune-release publish to overwrite
the dev-repo field specified in the opam file (#494, @samoht)dune-release not fail in the presence of ~/.dune/bin/dune (which is present
when using dune package management)dune-release no longer publishes docs to github pages. Instead, we rely on
the docs published under ocaml.org/packages (#499 #500, @v-gb @samoht)The Dune team is happy to announce the release of Dune 3.17.2!
This patch release includes some bug fixes. It brings some fixes for Melange
and Wasm_of_ocaml. It also fixes a bug that prevents the experimental feature,
package management, to build with ocaml.5.3.0.
melange.emit's compile_flags to the JS emission phase. (@anmonteiro,
#11252)We’re happy to announce that we just released ppxlib.0.34.0.
The full patch notes are available on the release page over here.
The main features are OCaml 5.3 compatibility, new AST pretty-printing utilities and the ppxlib-tools package, support for [@@deriving ...] on class types and the addition of missing Pprintast entry points.
ppxlib.0.34.0 is the first official ppxlib release that’s compatible with the new 5.3 compiler.
The ppxlib driver now also comes with a -keywords CLI option, similar to the compiler’s that allow you to compile and preprocess with the 5.3 compiler code that uses effect as an identifier. This is pretty niche but it’s there should you need it.
Please note that means you can use ppx-es with a 5.3 compiler but not that ppx-es can consume/produce 5.3 language features. We’re currently working on a fix allowing you to use the effect syntax in files that require preprocessing as it’s not possible with 0.34.0. The fix should be released in the next few days as 0.34.1.
We added a new Pp_ast module that allows you to pretty print AST fragments.
The only way ppxlib would print ASTs before were as S-expressions. In practice we found that it was not always helpful and wanted a more readable and human friendly way of displaying the AST.
The default output of those printer is a simplified version of the AST to keep things clear and avoid cluttering the output with information that is not always useful. For example, if you run Ppxlib.Pp_ast.Default.expression on the AST for x + 2, you’ll get the following:
Pexp_apply
( Pexp_ident (Lident "+")
, [ ( Nolabel, Pexp_ident (Lident "x"))
; ( Nolabel, Pexp_constant (Pconst_integer ( "2", None)))
]
)
The alert reader will note that there are no locations or attributes and that the expression record layer is omitted here.
You can of course configure the printer to display more information if you need to.
We’ve been using these new printers internally to debug migration code and they have been a huge help so we hope they will make working with ppxlib easier for you too.
In addition to this new module, we also added a command line utility called ppxlib-pp-ast to pretty print ASTs from source files, source code fragments or even marshalled AST files. It is very similar to the old ppx_tools’s dumpast.
Note that it will print ppxlib’s internal AST after it’s been migrated from the installed compiler’s version. This is something that we could not simply achieve with OCaml’s own -dparsetree.
This should be a useful tool for debugging ppx related bugs or learning about the AST and we hope ppx authors and users will like it.
As mentioned above, we also added some missing Pprintast* entries such as binding, longident and payload.
It is now possible to use [@@deriving ...] on class type declarations and therefore to write derivers for class types.
*: To the confused readers: Pprintast is entirely different from Pp_ast mentioned above as it prints the source code corresponding to a given AST.
We wanted to thank our external contributors for this release: @hhugo, @nojb and @dra27 for their help on the 5.3 compat and @mattiasdrp for bringing the Pprintast module up to speed.
Special thanks as well to @pedrobslisboa who started integrating their excellent ppx-by-example into ppxlib’s documentation.
Finally, I’d also like to thank the OCaml Software Foundation who’s been funding all my work on ppxlib and made this release possible!
Happy preprocessing to you all!
Add initial OCaml 5.3 support (#487, @NathanReb, @hhugo, @nojb)
Initialise OCaml 5.3's lexer with the keywords setting from OCAMLPARAM or
the new -keywords driver's CLI option to allow the standalone ppx driver to
process old packages using effect as an identifier
(#535, @dra27, @NathanReb)
Add Pprintast.binding, longident and payload (#542, @mattiasdrp)
Fix deriving_inline round-trip check so that it works with 5.01 <-> 5.02
migrations (#519, @NathanReb)
Add ppxlib's AST pretty-printing utilities in Ppxlib.Pp_ast and
a ppxlib-pp-ast executable in a new separate ppxlib-tools package
(#517, #525, #537, @NathanReb)
Change -dparsetree from a sexp output to a pretty printed AST, closer
to what the compiler's -dparsetree is.
(#530, @NathanReb)
Add Parsetree documentation comments to Ast_builder functions (#518, @patricoferris)
Support class type declarations in derivers with the new, optional arguments
{str,sig}_class_type_decl in Deriving.add (#538, @patricoferris)
We are excited to share the release of OCaml-LSP 1.20.1, which introduces powerful new features and vital bug fixes to improve your development workflow. The new typeSearch request allows you to find values by type signature or polarity, making it easier to locate the functionality you need. Configurable MerlinJump actions and the custom jump request give you more control over code navigation. On the bug fix side, we have tackled issues like file descriptor leaks, enhanced method completion, and cleaned up duplicate responses in selectionRange.
ocamllsp/typeSearch request (#1369)ocamllsp/jump request (#1374)merlinJumpCodeActions configuration option. Alternatively, a custom request is provided for ad hoc use of the feature. (#1411)selectionRange answers (#1368)This release introduces Merlin 5.3-502, compatible with OCaml 5.2, and 4.18-414, compatible with OCaml 4.14. Key updates include EXCLUDE_QUERY_DIR for better file management, resolving exceptions in polarity search,
and stabilizing type-enclosing results. For users of 5.3-502, additional enhancements address path resolution issues, fixes jump to fun functionality, and ensure proper handling of occurrences from hidden source files.
merlin binary
merlin binary (only in 5.3-502)
The Dune team is happy to announce the release of Dune 3.17.1!
This patch release includes some bug fixes. To reduce computing time, it does
not build .cmxs files anymore when the (no_dynlink) stanza is used instead.
This behavior also corrects the semantic of the (no_dynlink) stanza which was
building but not installing .cmxs files. It does not try to build and install them anymore.
When a library declares (no_dynlink), then the .cmxs file for it
is no longer built. (#11176, @nojb)
Fix bug that could result in corrupted file copies by Dune, for example when
using the copy_files# stanza or the copy# action. (@nojb, #11194, fixes
#11193)
Remove useless error message when running $ dune subst in empty projects.
(@rgrinberg, #11204, fixes #11200)
After almost a year of work, OCamlformat 0.27.0 is finally available with support for 5.3 syntax!
This release includes the new function syntax from OCaml 5.2, the effect
keyword from OCaml 5.3 and a large number of bug fixes and improvements.
An other notable change, is that comments are now formatted by default.
* Support OCaml 5.2 syntax (#2519, #2544, #2590, #2596, #2621, #2628, @Julow, @EmileTrotignon, @hhugo) This includes local open in types, raw identifiers, and the new representation for functions. This might change the formatting of some functions due to the formatting code being completely rewritten.
Support OCaml 5.3 syntax (#2609, #2610, #2611, #2622, #2623, #2562, #2624, #2625, #2627, @Julow, @Zeta611)
This adds support for effect patterns, short functor type arguments and utf8
identifiers.
To format code using the new effect syntax, add this option to your
.ocamlformat:
ocaml-version = 5.3
Documentation comments are now formatted by default (#2390, @Julow)
Use the option parse-docstrings = false to restore the previous behavior.
* Consistent indentation of polymorphic variant arguments (#2427, @Julow) Increases the indentation by one to make the formatting consistent with normal variants. For example:
...
(* before *)
(`Msg
(foo bar))
(* after *)
(`Msg
(foo bar))
Build on OCaml 5.3 (#2603, @adamchol, @Julow)
Improve the emacs plugin (#2577, #2600, @gridbugs, @thibautbenjamin) Allow a custom command to be used to run ocamlformat and add compatibility with emacs ocaml tree-sitter modes.
Added option let-binding-deindent-fun (#2521, @henrytill)
to control the indentation of the fun in:
let f =
fun foo ->
bar
Added back the flag --disable-outside-detected-project (#2439, @gpetiot)
It was removed in version 0.22.
Support newer Odoc syntax (#2631, #2632, #2633, @Julow)
* Consistent formatting of comments (#2371, #2550, @Julow) This is mostly an internal change but some comments might be formatted differently.
* Improve formatting of type constraints with type variables (#2437, @gpetiot) For example:
let f : type a b c.
a -> b -> c =
...
* Improve formatting of functor arguments (#2505, @Julow) This also reduce the indentation of functor arguments with long signatures.
Improvements to the Janestreet profile (#2445, #2314, #2460, #2593, #2612, @Julow, @tdelvecchio-jsc)
* Undo let-bindings and methods normalizations (#2523, #2529, @gpetiot) This remove the rewriting of some forms of let-bindings and methods:
let f x = (x : int) is no longer rewritten into let f x : int = xlet f (type a) (type b) ... is no longer rewritten into let f (type a b) ...let f = fun x -> ... is no longer rewritten into let f x = ...* The break-colon option is now taken into account for method type constraints (#2529, @gpetiot)
* Force a break around comments following an infix operator (fix non-stabilizing comments) (#2478, @gpetiot) This adds a line break:
a
||
(* this comment is now on its own line *)
b
open[@attr] M as open M [@@attr].[@ocamlformat "disable"] in some cases (#2242, #2525, @EmileTrotignon)
This caused a bug inside class type constructs and when attached to a let ... ina##b instead of a ## b and similarly for operators that start with # (#2580, @v-gb)break-separators=before (#2598, @Julow)let%ext (#2615, @Julow)We're happy to announce the release of Dune 3.17.0.
Among the list of chances, this release enables the Dune cache by default for
known-safe operations, adds support for Wasm_of_ocaml, adds support for the
-H compiler flag introduced in OCaml 5.2 and allows specifying code hosting
services like Codeberg or Gitlab organizations.
Show the context name for errors happening in non-default contexts. (#10414, fixes #10378, @jchavarri)
Correctly declare dependencies of indexes so that they are rebuilt when needed. (#10623, @voodoos)
Don't depend on coq-stdlib being installed when expanding variables
of the coq.version family (#10631, fixes #10629, @gares)
Error out if no files are found when using copy_files. (#10649, @jchavarri)
Re_export dune-section private library in the dune-site library stanza, in order to avoid failure when generating and building sites modules with implicit_transitive_deps = false. (#10650, fixes #9661, @MA0100)
Expect test fixes: support multiple modes and fix dependencies when there is a custom runner (#10671, @vouillon)
In a (library) stanza with (extra_objects) and (foreign_stubs), avoid
double linking the extra object files in the final executable.
(#10783, fixes #10785, @nojb)
Map (re_export) library dependencies to the exports field in META files,
and vice-versa. This field was proposed in to
https://discuss.ocaml.org/t/proposal-a-new-exports-field-in-findlib-meta-files/13947.
The field is included in Dune-generated META files only when the Dune lang
version is >= 3.17.
(#10831, fixes #10830, @nojb)
Fix staged pps preprocessors on Windows (which were not working at all previously) (#10869, fixes #10867, @nojb)
Fix dune describe when an executable is disabled with enabled_if.
(#10881, fixes #10779, @moyodiallo)
Fix an issue where C stubs would be rebuilt whenever the stderr of Dune was redirected. (#10883, fixes #10882, @nojb)
Fix the URL opened by the command dune ocaml doc. (#10897, @gridbugs)
Fix the file referred to in the error/warning message displayed due to the dune configuration version not supporting a particular configuration stanza in use. (#10923, @H-ANSEN)
Fix enabled_if when it uses env variable. (#10936, fixes #10905, @moyodiallo)
Fix exec -w for relative paths with --root argument (#10982, @gridbugs)
Do not ignore the (locks ..) field in the test and tests stanza
(#11081, @rgrinberg)
Tolerate files without extension when generating merlin rules. (#11128, @anmonteiro)
Make Merlin/OCaml-LSP aware of "hidden" dependencies used by
(implicit_transitive_deps false) via the -H compiler flag. (#10535, @voodoos)
Add support for the -H flag (introduced in OCaml compiler 5.2) in dune
(requires lang versions 3.17). This adaptation gives
the correct semantics for (implicit_transitive_deps false).
(#10644, fixes #9333, ocsigen/tyxml#274, #2733, #4963, @MA0100)
Add support for specifying Gitlab organization repositories in source
stanzas (#10766, fixes #6723, @H-ANSEN)
New option to control jsoo sourcemap generation in env and executable stanza (#10777, fixes #10673, @hhugo)
One can now control jsoo compilation_mode inside an executable stanza (#10777, fixes #10673, @hhugo)
Add support for specifying default values of the authors, maintainers, and
license stanzas of the dune-project file via the dune config file. Default
values are set using the (project_defaults) stanza (#10835, @H-ANSEN)
Add names to source tree events in performance traces (#10884, @jchavarri)
Add codeberg as an option for defining project sources in dune-project
files. For example, (source (codeberg user/repo)). (#10904, @nlordell)
dune runtest can now run individual tests with dune runtest mytest.t
(#11041, @Alizter).
Wasm_of_ocaml support (#11093, @vouillon)
Add a coqdep_flags field to the coq field of the env stanza, and to the
coq.theory stanza, allowing to configure coqdep flags. (#11094,
@rlepigre)
Remove all remnants of the experimental patch-back-source-tree. (#10771,
@rgrinberg)
Change the preset value for author and maintainer fields in the
dune-project file to encourage including emails. (#10848, @punchagan)
Tweak the preset value for tags in the dune-project file to hint at topics
not having a special meaning. (#10849, @punchagan)
Change some colors to improve readability in light-mode terminals (#10890, @gridbugs)
Forward the linkall flag to jsoo in whole program compilation as well (#10935, @hhugo)
Configurator uses pkgconf as pkg-config implementation when available
and forwards it the target of ocamlc -config. (#10937, @pirbo)
Enable Dune cache by default. Add a new Dune cache setting
enabled-except-user-rules, which enables the Dune cache, but excludes
user-written rules from it. This is a conservative choice that can avoid
breaking rules whose dependencies are not correctly specified. This is the
current default. (#10944, #10710, @nojb, @ElectreAAS)
Do not add dune dependency in dune-project when creating projects with
dune init proj. The Dune dependency is implicitely added when generating
opam files (#11129, @Leonidas-from-XIV)
Feedback on this post is welcomed on Discuss!
As mentioned in our talk at the OCaml Workshop 2024, we decided to switch to a time-based release cycle (every 6 months), starting with opam 2.3.
As promised, we are very pleased to announce the release of opam 2.3.0, and encourage all users to upgrade. Please read on for installation and upgrade instructions.
In case you plan a possible rollback, you may want to first backup your
~/.opam or $env:LOCALAPPDATA\opam directory.
The upgrade instructions are unchanged:
For Unix systems
bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh)"
or from PowerShell for Windows systems
Invoke-Expression "& { $(Invoke-RestMethod https://opam.ocaml.org/install.ps1) }"
or download manually from the Github "Releases" page to your PATH.
You should then run:
opam init --reinit -ni
When loading a repository, opam now ignores files in packages' files/ directories which aren't listed in the extra-files field of the opam file.
This was done to simplify the opam specification where we hope the opam file to be the only thing that you have to look at when reading a package specification. It being optional to list all files in the extra-files: field went against that principle. This change also reduces the surface area for potential file corruption as all extra-files must have checksums.
This is a breaking change and means that if you are using the files/ directory without listing them in the extra-files: field, you need to make sure that all files in that directory are included in the extra-files field.
The resulting opam file remains compatible with all previous opam 2.x releases.
If you have an opam repository, you should make sure all files are listed so every packages continues to work without any issue, which can be done automatically using the opam admin update-extrafiles command.
Packages requiring an unsupported version of opam are now marked unavailable, instead of causing a repository error. This means an opam repository can now allow smoother upgrade in the future where some packages can require a newer version of opam without having to fork the repository to upgrade every package to that version as was done for the upgrade from opam 1.2 to 2.0
Add a new opam list --latests-only option to list only the latest versions of packages. Note that this option respects the order options were given on the command line. For example: --available --latests-only will first list all the available packages, then choose only the latest packages in that set; while --latests-only --available will first list all the latest packages, then only show the ones that are available in that set
Fix and improve opam install --check, which now checks if the whole dependency tree of the package is installed instead of only the root dependencies
Add a new --verbose-on option to enable verbose output for specified package names. Thanks to @desumn for this contribution
Add a new opam switch import --deps-only option to install only the dependencies of the root packages listed in the opam switch export file
opam switch list-available no longer displays compilers flagged with avoid-version/deprecated unless --all is given, meaning that pre-release or unreleased OCaml packages no longer appear to be the latest version
opam switch create --repositories now correctly infers --kind=git for URLs ending with .git rather than requiring the git+https:// protocol. This is consistant with other commands such as opam repository add. Thanks to @Keryan-dev for this contribution
opam switch set-invariant now displays the switch invariant using the same syntax as the --formula flag
The builtin-0install solver was improved and should now be capable of being your default solver instead of builtin-mccs+glpk. It was previously mostly only suited for automated tasks such as Continuous Integration. If you wish to give it a try, simply calling opam option solver=builtin-0install (call opam option solver= restores the default)
Most of the unhelpful conflict messages were fixed. (#4373)
Fix an opam 2.1 regression where the initial pin of a local VCS directory would store untracked and ignored files. Those files would usually be cleaned before building the package, however git submodules would not be cleaned and would cause issues when paired with the new behaviour added in 2.3.0~alpha1 which makes opam error when git submodules fail to update (it was previously a warning). (#5809)
Fix the value of the arch variable when the current OS is 32bit on a 64bit machine (e.g. Raspberry Pi OS). (#5949)
opam now fails when git submodules fail to update instead of ignoring the error and just showing a warning
opam's libraries now compile with OCaml >= 5.0 on Windows
Fix the installed packages internal cache, which was storing the wrong version of the opam file after a build failure. This could be triggered easily for users with custom repositories with non-populated extra-files. (#6213)
Several improvements to the pre-built release binaries were made:
And many other general, performance and UI improvements were made and bugs were fixed. You can take a look to previous blog posts. API changes and a more detailed description of the changes are listed in:
This release also includes PRs improving the documentation and improving and extending the tests.
Please report any issues to the bug-tracker.
We hope you will enjoy the new features of opam 2.3!
We're happy to announce the release of Dune 3.16.1.
This is a patch release that fixes an issue with OCaml.5.3.0 and C++ flags.
-std=gnu++11 when using OCaml >= 5.0
(#10962, @kit-ty-kate)
We are happy to announce the joint release of Merlin 5.2.1-502 and 4.17.1. This release adds many new features to Merlin including the ability to add hints to a source tree, serch for values using a type signature and expanding PPX annotations to preview their source code. There are also bug fixes for both the Merlin binary and editor modes.
More information can be found in the Discuss announcement.
Contributions are always welcome at Merlin | Issues
-unboxed-types and -no-unboxed-types as OCaml ignored flags (ocaml/merlin#1795, fixes ocaml/merlin#1794)expand-node command for expanding PPX annotations (ocaml/merlin#1745)inlay-hints command for adding hints on a source tree (ocaml/merlin#1812)search-by-type command for searching values by types (ocaml/merlin#1828)dot-merlin-reader ignoring SOURCE_ROOT and STDLIB directives (ocaml/merlin#1839, ocaml/merlin#1803)merlin.py (ocaml/merlin#1798)merlin-search-by-type, merlin-search-by-polarity and change the behaviour of merlin-search to switch between by-type or by-polarity depending on the query (ocaml/merlin#1828)Hello folks! 👋
We'd like to welcome everyone to try and play with the Dune Developer Preview! 🎉
This experimental nightly release of dune includes a lot of improvements, including the much expected package management features, and it can be installed from that website or by using the new installation script:
$ curl -fsSL https://get.dune.build/install | bash
In a few seconds you should be ready to OCaml by calling dune:
You can also watch and share this demo on X and Mastodon.
Please try it out and let us know what you think 🙏
📅 You can book a feedback call with us here
📝 You can submit feedback using this form
🐛 You can submit issues to Github on ocaml/dune
The Dune shared cache has been enabled by default. We're starting off by caching all downloads and dependencies.
We have improved support for dev tools. We're working to streamline this but in the latest binary you can:
Configure your LSP (in Neovim, Vim, Emacs, etc) to call dune tools exec ocamllsp to get LSP support for your projects out of the box – this may take a little bit the first time it builds the LSP for a compiler version, but it's pretty much instant afterwards.
Call dune fmt to get your project formatted – remember to add an .ocamlformat file if you don't have one yet. An empty one is enough.
Call dune ocaml doc to get documentation built
We're looking forward to streamlining the DX, working on better dependency locks, and looking into supporting Windows.
In particular, we're considering work on a few things:
dune create <repo> – to let the community create templates that can be easily used from within dunedune pkg fetch – to prefetch packages and prepare a repository for working in offline modedune build @deps - to build all dependencies, useful for staged builds in Dockerfilesdune pkg add <name> - to make adding packages straightforwardIf you've got any ideas, we'd love to hear them, so please open a feature request on Github 🙏
At FunOCaml we had a last-minute opportunity to present the work being done on Dune and we used it to introduce the Developer Preview to the community, and even tested Package Management live with suggestions from the audience (thanks @anmonteiro and Paul-Elliot for participating!) – you can watch it on Twitch.
We're working with @Claire_Vandenberghe on redesigning the Developer Preview website so that it'd feel like a seamless extension of OCaml.org – in this current iteration we've made it easier to get started and we're putting the FAQ front and center.
We'll be iterating on this design in the coming weeks until it fits perfectly within the OCaml.org design system 🎨
You can check the new website here: https://preview.dune.build
In the near future we'll be publishing blog posts about the Developer Preview and Package Management, which we're working on with @professor.rose 👏
As we prepare for the public beta, we're ramping up the DX interviews and ensuring the first few users will have a fun, productive experience with the Developer Preview.
📥 If you signed up for the Dev Preview back in May, check your inbox for a link and instructions to schedule your DX interview with us.
Here's a sample video on (Mastodon or X) where you can see us building the Riot project on a machine that does not have OCaml installed. It is pretty neat!
Seriously, big shoutout to the Dune team at Tarides[0] and Jane Street[1] who have been doing a phenomenal job 👏 ✨ 🐫
So here's what getting started with OCaml looks like using the Dune Developer Preview as of today (August 19 2024):
dune from our binary distribution – we'll soon make this public!dune pkg lock in your favorite projectdune buildThat's it. No need to install anything else! Dune will see that lock file, fetch, and build all necessary dependencies.
🗺️ These are some strong steps towards the OCaml Platform vision for 2026 that we are actively working towards. If you have any thoughts or feedback please let us know!
There are more improvements coming that will help remove friction to get started and create a delightful experience. Both of these things we strongly believe will help onboard new users to the OCaml world.
Here's a few in the works:
Various DX improvements – from new outputs to simplified workflows, we want to make using Dune just delightful.
Bundled support for dev tools (OCamlFormat, odoc, LSP) – the default toolset will be available without any extra steps! Just call dune fmt and it works. No need to manually install anything else.
Automatic dependency locking – when building, and even in watch mode, Dune will lock your dependencies by default and keep the lock up to date.
Cross-project caching – by default we'll enable a local Dune cache across the system, so you never rebuild the same dependency, even across projects.
Signed binaries with certificates of origin – we care deeply about security and want to make sure that any binary we ship can be easily verified and tracked back to its sources.
Stay tuned! 👋
PS: here's a longer video on (Mastodon or X) showing you the setup for OCaml from zero, creating a new project, and adding a dependency, all within ~5 minutes
[0] @emillon @Leonidas @gridbugs @tmattio @maiste . Ambre Suhamy, Alpha Diallo [1] @rgrinberg
Feedback on this post is welcomed on Discuss!
We are pleased to announce the release of opam 2.2.1.
We've fixed a couple of regressions and would like to encourage users of opam 2.2 to upgrade.
The three main changes are:
opam install --deps-only where the direct dependencies were not set as root packages
(spotted in the wild by @rjbou and also reported on Discuss)--write-out to --fail
if exit code 43 is returned by Curl. In particular, this fixes opam init when run from cmd/PowerShell on Windows 11 23H2
(#6120)A couple more improvements and additions to the testsuite were made. You can view the full list of changes in the release note.
The upgrade instructions are unchanged:
For Unix systems
bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh) --version 2.2.1"
or from PowerShell for Windows systems
Invoke-Expression "& { $(Invoke-RestMethod https://opam.ocaml.org/install.ps1) }"
(or via winget upgrade OCaml.opam) or download manually from the Github "Releases" page to your PATH.
You should then run:
opam init --reinit -ni
Please report any issues to the bug-tracker.
Happy hacking!
We are pleased to announce the release of OCaml LSP 1.19.0. This version brings official support for OCaml 5.2. It also includes a new custom query to get
documentation and a fix regarding the handling of OCamlFormat processes.
ocamllsp/getDocumentation request (ocaml/ocaml-lsp#1336)sigterm rather than sigint or sigkill (ocaml/ocaml-lsp#1343)The Ppxlib dev team is happy to announce the release of ppxlib.0.33.0.
This release's main feature is a series of improvement to flags controlling
unused value/module/type warnings silencing.
The ppxlib driver generates warning silencing items to prevent [@@deriving ...]
generated code to trigger unused code warnings. Three warnings are disabled that
way:
[@@deriving ...] attribute is attached.
This feature was added a long time ago to avoid manually disabling those
warnings when working with derivers that generate a set of values and modules
only to use a subset of those. Alternatively, the unused type warning silencing
was added to allow defining an alias type only to be consumed by a deriver (e.g.,
type error = [`Not_found | `Invalid_arg] [@@deriving to_string]).
We since then believe that we should not disable warnings lightly, as this
behaviour makes it difficult to find and remove deadcode. The right approach in
those situations should be to fix the PPX derivers so that they are more
configurable and can be used without triggering such warnings.
We will start to move toward removing this feature, but since it is still useful in
some places, we came up with a plan to do this iteratively.
In ppxlib.0.31.0 we added the -unused-code-warnings driver flag and the
?unused_code_warnings Deriving.V2.make optional argument to control whether
to silence Warnings 32 and 60. When both are set to true, by the user and the
deriver authors, the warnings are not silenced. As of ppxlib.0.33.0, these also
control the silencing of Warning 34 (unused type).
force can now be passed to the -unused-code-warnings flag in order to
disable warnings silencing, regardless of the derivers opting in. This allows
users to test whether their codebase and their set of derivers rely on warning
silencing or not and to use those results to eliminate deadcode and/or report
issues upstream to the derivers they use.
We also added a separate -unused-type-warnings flag that works similarly to
-unused-code-warnings (i.e., depends on the value of the
?unused_code_warnings argument), but it only controls Warning 34 silencing, as it
turns out it is less likely to cause unwanted warnings than with the other two.
This will allow users to disable it more easily, without having to deal with
Warnings 32 and 60 straight away.
We want to encourage users to try those on their codebase in order to see the impact
it has. Did you have deadcode lying around that slipped past undetected? Does
this trigger unwanted warnings because of deriver's generated code?
The plan is to give the ecosystem some time to try those features and adapt by fixing
individual derivers and flipping setting ?unused_code_warnings to true as they
do. After a while, we will swap the default value of the driver flag to true so
that only derivers that haven't opted in will enable warning silencing. Then as
time goes we will swap the default of the Deriving.make argument so that
derivers will instead have to explicitly opt out to get the warning silencing.
Finally, once we are confident the ecosystem is in a good enough state, we will
remove this feature altogether.ppxlib.0.33.0 also comes with a couple of new features for PPX authors:
Ast_builder functions: elist_tail and plist_tail
that can be used to build list expressions and patterns with a custom tail:
elist_tail [expr1; expr2] tail_expr returns the expression for
expr1::expr2::tail_expr.Context_free.special_function', a new version of special_function that
allows passing a Longident.t directly rather that relying on parsing the
string argument to a Longident.t.Finally, the release includes a few bug fixes to Longident.parse and
Code_path.main_module_name and fixes the location-check flag so it is not
required to also pass -check to enable location checks. It also fixes the 5.2
migrations locations, as we used to build nodes with inconsistent locations when
migrating Pexp_function nodes.
We would like to thank our external contributors who have been a huge part of this release: @octachron, @vg-b, and @jchavarri, and a special mention to @mbarbin, who has not only contributed a lot to the warning silencing features but has been extensively testing and providing very useful feedback on them.
And of course, as usual, we'd like to thank the OCaml Software Foundation who has been funding my work on Ppxlib and on this release, making all of this possible!
Fix a bug where Code_path.main_module_name would not properly remove
extensions from the filename and therefore return an invalid module name.
(#512, @NathanReb)
Add -unused-type-warnings flag to the driver to allow users to disable
only the generation of Warning 34 silencing structure items when using
[@@deriving ...] on type declarations. (#511, @mbarbin, @NathanReb)
Make the -unused-code-warnings driver flag also control Warning 34
silencing for type declarations with [@@deriving ...] attached.
(#510, @mbarbin, @NathanReb)
Add -unused-code-warnings=force driver command-line flag argument. (#490, @mbarbin)
Add new functions Ast_builder.{e,p}list_tail that take an extra tail
expression/pattern argument parameter compared to Ast_builder.{e,p}list, so
they can build ASTs like a :: b :: c instead of only [ a; b ].
(#498, #502, @v-gb, @NathanReb)
Fix Longident.parse so it also handles indexing operators such as
.!(), .%(;..)<-, or Vec.(.%()) (#494, @octachron)
Add a special_function' variant that directly takes a Longident.t
argument in order to avoid the issue with Longident.t covering distinct
syntactic classes that cannot be easily parsed by a common parser (#496, @octachron).
Keep location ranges consistent when migrating Pexp_function nodes from 5.2+
to older versions (#504, @jchavarri)
Fix -locations-check behaviour so it is no longer required to pass -check and
can enable location checks. (#506, @NathanReb)
We are pleased to announce the release of OCaml LSP 1.18.0. This version comes with a lot of fixes and new features.
Notable features that are included in this release are:
TypeEnclosingifthenelse expressions...and many fixes to a handful of issues.
Feedback is very much welcomed on the the Discuss Announcement post and do not hesistate to report issues in the issue tracker.
Introduce a configuration option to control Dune diagnostics. The option is called duneDiganostics, and it may be set to { enable: false } to disable diagnostics. (ocaml/ocaml-lsp#1221)
Support folding of ifthenelse expressions (ocaml/ocaml-lsp#1031)
Improve hover behavior (ocaml/ocaml-lsp#1245)
Hovers are no longer displayed on useless parse tree nodes such as keywords, comments, etc.
Multiline hovers are now filtered away.
Display expanded PPXs in the hover window.
Improve document symbols (ocaml/ocaml-lsp#1247)
Use the parse tree instead of the typed tree. This means that document symbols will work even if the source code doesn't type check.
Include symbols at arbitrary depth.
Differentiate functions / types / variants / etc.
This now includes PPXs like let%expect_test or let%bench in the outline.
Introduce a destruct-line code action. This is an improved version of the
old destruct code action. (ocaml/ocaml-lsp#1283)
Improve signature inference to only include types for elements that were absent from the signature. Previously, all signature items would always be inserted. (ocaml/ocaml-lsp#1289)
Add an update-signature code action to update the types of elements that
were already present in the signature (ocaml/ocaml-lsp#1289)
Add custom
ocamllsp/merlinCallCompatible
request (ocaml/ocaml-lsp#1265)
Add custom ocamllsp/typeEnclosing request (ocaml/ocaml-lsp#1304)
Detect document kind by looking at Merlin's suffixes config.
This enables more LSP features for non-.ml/.mli files. Though it still
depends on Merlin's support. (ocaml/ocaml-lsp#1237)
Correctly accept the --clientProcessId flag. (ocaml/ocaml-lsp#1242)
Disable automatic completion and signature help inside comments (ocaml/ocaml-lsp#1246)
Includes a new optional/configurable option to toggle syntax documentation. If toggled on, allows display of syntax documentation on hover tooltips. Can be controlled via environment variables and by GUI for VS code. (ocaml/ocaml-lsp#1218)
For completions on labels that the LSP gets from Merlin, take into account
whether the prefix being completed starts with ~ or ?. Change the label
completions that start with ? to start with ~ when the prefix being
completed starts with ~. (ocaml/ocaml-lsp#1277)
Fix document syncing (ocaml/ocaml-lsp#1278, ocaml/ocaml-lsp#1280, fixes ocaml/ocaml-lsp#1207)
Stop generating inlay hints on generated code (ocaml/ocaml-lsp#1290)
Fix parenthesising of function types in SignatureHelp (ocaml/ocaml-lsp#1296)
Fix syntax documentation rendering (ocaml/ocaml-lsp#1318)
Feedback on this post is welcomed on Discuss!
We are very pleased to announce the release of opam 2.2.0, and encourage all users to upgrade. Please read on for installation and upgrade instructions.
In case you plan a possible rollback, you may want to first backup your
~/.opam or $env:LOCALAPPDATA\opam directory.
The upgrade instructions are unchanged:
For Unix systems
bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh) --version 2.2.0"
or from PowerShell for Windows systems
Invoke-Expression "& { $(Invoke-RestMethod https://opam.ocaml.org/install.ps1) }"
or download manually from the Github "Releases" page to your PATH.
You should then run:
opam init --reinit -ni
After 8 years' effort, opam and opam-repository now have official native Windows support! A big thank you is due to Andreas Hauptmann (@fdopen), whose WODI and OCaml for Windows projects were for many years the principal downstream way to obtain OCaml on Windows, Jun Furuse (@camlspotter) whose initial experimentation with OPAM from Cygwin formed the basis of opam-repository-mingw, and, most recently, Jonah Beckford (@jonahbeckford) whose DkML distribution kept - and keeps - a full development experience for OCaml available on Windows.
OCaml when used on native Windows requires certain tools from the Unix world
which are provided by either Cygwin or MSYS2.
We have engineered opam init so that it is possible for a user not to need to
worry about this, with opam managing the Unix world, and the user being able
to use OCaml from either the Command Prompt or PowerShell. However, for the Unix
user coming over to Windows to test their software, it is also possible to have
your own Cygwin/MSYS2 installation and use native Windows opam from that. Please
see the previous blog post
for more information.
There are two "ports" of OCaml on native Windows, referred to by the name of provider of the C compiler. The mingw-w64 port is GCC-based. opam's external dependency (depext) system works for this port (including providing GCC itself), and many packages are already well-supported in opam-repository, thanks to the previous efforts in opam-repository-mingw. The MSVC port is Visual Studio-based. At present, there is less support in this ecosystem for external dependencies, though this is something we expect to work on both in opam-repository and in subsequent opam releases. In particular, it is necessary to install Visual Studio or Visual Studio BuildTools separately, but opam will then automatically find and use the C compiler from Visual Studio.
opam tree is a new command showing packages and their dependencies with a tree view.
It is very helpful to determine which packages bring which dependencies in your installed switch.
$ opam tree cppo
cppo.1.6.9
├── base-unix.base
├── dune.3.8.2 (>= 1.10)
│ ├── base-threads.base
│ ├── base-unix.base [*]
│ └── ocaml.4.14.1 (>= 4.08)
│ ├── ocaml-base-compiler.4.14.1 (>= 4.14.1~ & < 4.14.2~)
│ └── ocaml-config.2 (>= 2)
│ └── ocaml-base-compiler.4.14.1 (>= 4.12.0~) [*]
└── ocaml.4.14.1 (>= 4.02.3) [*]
Reverse-dependencies can also be displayed using the new opam why command.
This is useful to examine how dependency versions get constrained.
$ opam why cmdliner
cmdliner.1.2.0
├── (>= 1.1.0) b0.0.0.5
│ └── (= 0.0.5) odig.0.0.9
├── (>= 1.1.0) ocp-browser.1.3.4
├── (>= 1.0.0) ocp-indent.1.8.1
│ └── (>= 1.4.2) ocp-index.1.3.4
│ └── (= version) ocp-browser.1.3.4 [*]
├── (>= 1.1.0) ocp-index.1.3.4 [*]
├── (>= 1.1.0) odig.0.0.9 [*]
├── (>= 1.0.0) odoc.2.2.0
│ └── (>= 2.0.0) odig.0.0.9 [*]
├── (>= 1.1.0) opam-client.2.2.0~alpha
│ ├── (= version) opam.2.2.0~alpha
│ └── (= version) opam-devel.2.2.0~alpha
├── (>= 1.1.0) opam-devel.2.2.0~alpha [*]
├── (>= 0.9.8) opam-installer.2.2.0~alpha
└── user-setup.0.7
Special thanks to @cannorin for contributing this feature.
There is now a way for a project maintainer to share their project development
tools: the with-dev-setup dependency flag. It is used in the same way as
with-doc and with-test: by adding a {with-dev-setup} filter after a
dependency. It will be ignored when installing normally, but it's pulled in when the
package is explicitly installed with the --with-dev-setup flag specified on
the command line.
For example
opam-version: "2.0"
depends: [
"ocaml"
"ocp-indent" {with-dev-setup}
]
build: [make]
install: [make "install"]
post-messages:
[ "Thanks for installing the package"
"as well as its development setup. It will help with your future contributions" {with-dev-setup} ]
When pinning a package using opam pin, opam looks for opam files in the root directory only.
With recursive pinning, you can now instruct opam to look for .opam files in
subdirectories as well, while maintaining the correct relationship between the .opam
files and the package root for versioning and build purposes.
Recursive pinning is enabled by the following options to opam pin and opam install:
--recursive, opam will look for .opam files recursively in all subdirectories.--subpath <path>, opam will only look for .opam files in the subdirectory <path>.The two options can be combined: for instance, if your opam packages are stored
as a deep hierarchy in the mylib subdirectory of your project you can try
opam pin . --recursive --subpath mylib.
These options are useful when dealing with a large monorepo-type repository with many opam libraries spread about.
opam switch -, inspired by git switch -, makes opam switch back to the previously
selected global switch.
opam pin --current fixes a package to its current state (disabling pending
reinstallations or removals from the repository). The installed package will
be pinned to its current installed state, i.e. the pinned opam file is the
one installed.
opam pin remove --all removes all the pinned packages from a switch.
opam exec --no-switch removes the opam environment when running a command.
It is useful when you want to launch a command without opam environment changes.
opam clean --untracked removes untracked files interactively remaining
from previous packages removal.
opam admin add-constraint <cst> --packages pkg1,pkg2,pkg3 applies the given constraint
to a given set of packages
opam list --base has been renamed into --invariant, reflecting the fact that since opam 2.1 the "base" packages of a switch are instead expressed using a switch invariant.
opam install --formula <formula> installs a formula instead of a list of packages. This can be useful if you would like to install one package or another one. For example opam install --formula '"extlib" |"extlib-compat"' will install either extlib or extlib-compat depending on what's best for the current switch.
opam env, fixing many corner cases for environment updates and making the reverting of package environment variables precise. As a result, using setenv in an opam file no longer triggers a lint warning.sys-ocaml-system default global eval variable"%{var?string-if-true:string-if-false-or-undefined}%" syntax to
support extending the variables of packages with + in their name
(conf-c++ and conf-g++ already exist) using "%{?pgkname:var:}%"getconf DARWIN_USER_TEMP_DIR) as writable when TMPDIR
is not defined on macOS/tmp is now writable again, restoring POSIX complianceopam admin: new add-extrafiles command to add/check/update the extra-files: field according to the files present in the files/ directoryopam lint -W @1..9 syntax to allow marking a set of warnings as errorsOPAMCURL, OPAMFETCH and OPAMVERBOSE environment variables--assume-built argumentAnd many other general and performance improvements were made and bugs were fixed. You can take a look to previous blog posts. API changes and a more detailed description of the changes are listed in:
This release also includes PRs improving the documentation and improving and extending the tests.
Please report any issues to the bug-tracker.
We hope you will enjoy the new features of opam 2.2! 📯
We are pleased to announce the release of Merlin 5.1-502. This is an important release that brings a lot of backend changes and a major
new feature: project-wide occurrences queries.
Try it by running dune build @ocaml-index (since dune 3.16.0) and performing a reference query!
More information can be found in the discuss announcement and the wiki.
Merlin_lib.index_formatSOURCE_ROOT that is used to resolve relative paths found in the
indexes.INDEX that is used to declare the list of index files Merlin should
use when looking for occurrences.UNIT_NAME configuration directive that can be used to tell Merlin
the correct name of the current unit in the presence of wrapping (ocaml/merlin#1776)merlin-lib.commands: Add a find_command_opt alternative to
find_command that does not raise (ocaml/merlin#1778)We're happy to announce the release of Dune 3.16.0.
Among the list of chances, this release contains improvements to Melange support and a way to look for references in a whole project using Merlin and OCaml LSP.
Allow libraries with the same (name ..) in projects as long as they don't
conflict during resolution (via enabled_if). (#10307, @anmonteiro,
@jchavarri)
dune describe pp now finds the exact module and the stanza it belongs to,
instead of guessing the name of the preprocessed file. (#10321, @anmonteiro)
Print the result of dune describe pp with the respective dialect printer.
(#10322, @anmonteiro)
Add new flag --context to dune ocaml-merlin, which allows to select a
Dune context when requesting Merlin config. Add dune describe contexts
subcommand. Introduce a field generate_merlin_rules for contexts declared
in the workspace, that allows to optionally produce Merlin rules for other
contexts besides the one selected for Merlin (#10324, @jchavarri)
Melange: add include paths for private library .cmj files during JS
emission. (#10416, @anmonteiro)
dune ocaml-merlin: communicate additional directives SOURCE_ROOT,
UNIT_NAME (the actual name with wrapping) and INDEX with the paths to the
index(es). (#10422, @voodoos)
Add a new alias @ocaml-index that uses the ocaml-index binary to generate
indexes that can be read by tools such as Merlin to provide project-wide
references search. (#10422, @voodoos)
Merlin: add optional (merlin_reader CMD) construct to (dialect) stanza to
configure a Merlin reader (#8567, @andreypopp)
Melange: treat private libraries with (package ..) as public libraries,
fixing an issue where import paths were wrongly emitted. (#10415,
@anmonteiro)
Install .glob files for Coq theories too (#10602, @ejgallego)
Don't try to document nonexistent libraries in doc-new target (#10319, fixes #10056, @jonludlam)
Make dune-site's load_all function look for META files so that it
doesn't fail on empty directories in the plugin directory (#10458, fixes
#10457, @shym)
Fix incorrect warning for libraries defined inside nonexistant directories
using (subdir ..) and used by executables using dune-build-info (#10525,
@rgrinberg)
Don't try to take build lock when running coq top --no-build (#10547, fixes
#7671, @lzy0505)
Make sure to truncate Dune's lock file after locking and unlocking so that users cannot observe incorrect PID's (#10575, @rgrinberg)
MDX: link MDX binary with byte_complete. This fixes (libraries) with
foreign archives on Linux. (#10586, fixes #10582, @anmonteiro)
Virtual libraries: fix an issue where linking an executable involving several virtual libries would cause an error. (#10581, fixes #10460, @rgrinberg)
We are pleased to announce the release of Merlin 4.16-414 and 4.16-501.
These releases expose additional functions for packages using merlin-lib that need to manually parse merlin commands.
merlin-lib.commands library which disassociates the
execution of commands from the new_protocol, from the binary, allowing
it to be invoked from other projects (ocaml/merlin#1758)merlin-lib.commands: Add a find_command_opt alternative to
find_command that does not raise (ocaml/merlin#1778)We are pleased to announce the release of Merlin 4.15-414 and 4.15-501.
These releases bring a handful of bug fixes and improvements, notably to the
destruct feature, that were already released for OCaml 5.2 in Merlin 5.0-502.
We just released version 3.15.3 with some bug fixes.
Fix interpretation of exists_if predicate in META files of installed
libraries containing more than one element. (#10564, fixes #10563, @dbuenzli, @nojb)
Fix TSAN warning in wait4 stubs (#10554, fixes #10553, @emillon)
Feedback on this post is welcomed on Discuss!
We are pleased to announce the patch release of opam 2.1.6.
This opam release consists of backported bug fixes and improvements:
Opam installation instructions (unchanged):
From binaries: run
bash -c "sh <(curl -fsSL https://opam.ocaml.org/install.sh) --version 2.1.6"
or download manually from the Github "Releases" page to your PATH. In this case, don't forget to run opam init --reinit -ni to enable sandboxing if you had version 2.0.0~rc manually installed or to update you sandbox script.
From source, using opam:
opam update; opam install opam-devel
(then copy the opam binary to your PATH as explained, and don't forget to run opam init --reinit -ni to enable sandboxing if you had version 2.0.0~rc manually installed or to update your sandbox script)
From source, manually: see the instructions in the README.
We hope you enjoy this new minor version, and remain open to bug reports and suggestions.
GNU patch is not detected when a patch is applied
[#5893 @kit-ty-kate]gpatch by default instead of patch on NetBSD and DragonFlyBSD
[#5893 @kit-ty-kate]gpatch if it exists and is detected as GNU patch when patch is not
GNU patch [#5893 @kit-ty-kate]OpamSystem.patch now displays a warning when GNU patch is not detected
and looks for both patch and gpatch as a backup option depending on the OS
[#5893 @kit-ty-kate]We are pleased to announce the release of Merlin 5.0-502!
This release brings official support for OCaml 5.2. Substantial backend changes were required to adapt to this release, especially for features such as occurrences and get-documentation. Do not hesitate to report any suspicious behavior in the issue tracker!
This release also fixes a handful of issues, two of them improving the behaviour of Merlin's destruct feature.
destruct: Removal of residual patterns (#1737, fixes #1560)merlin-lib.commands library that disassociates the
execution of commands from the new_protocol, from the binary, allowing
it to be invoked from other projects (#1758)merlin.hide
attribute is present. (#1768)uid_to_decl table in 5.2's CMT files to get documentation.
(#1773)The ppxlib team is happy to announce the release of ppxlib.0.32.1.
The main feature of this release is of course the support for the upcoming OCaml 5.2 release. Starting with this version you'll be able to use ppx with the latest compiler.
The feature also comes with a small follow up improvement to the 0.32.0 error reporting changes that simplifies how exception thrown from context free rewriting are handled. The errors will now be inserted where the generated code would have been instead of appended to the whole AST. This should lead to a better error reporting from the compiler as it will now report errors in order of their position in the code.
We'd like to thank the OCaml Software Foundation once again as they funded the vast majority of the work for this release.
Add support for OCaml 5.2
Insert errors from caught located exceptions in place of the code that should have been generated by context-free rules. (#472, @NathanReb)
We've released odoc 2.4.2 with OCaml 5.2 compatibility and a few bug fixes.
We've released OCamlFormat 0.26.2 with compatibility with OCaml 5.2.
We just released version 3.15.2 with some bug fixes.
This one is particularly important for Coq users since it fixes a bug introduced in 3.13.0 that made incremental builds very slow.
If no directory targets are defined, then do not evaluate enabled_if
(#10442, @rgrinberg)
Fix a bug where Coq projects were being rebuilt from scratch each time the dependency graph changed. (#10446, fixes #10149, @alizter)
This release reverts the change introduce in Mdx 2.4.0 that allows the execution of included OCaml code blocks after users reported issues. We will revisit the feature to ensure it is opt-in and doesn't break users setup.
We're happy to announce that Dune 3.15.0 is now available. This feature has many fixes and new features that you can find in the changelog.
There are a few new features that we would like to specially highlight.
Prior to Dune 3.15 there were a number of limitations where percent forms like
%{env:...} could be used to expand to useful values. In this release,
@rgrinberg put some effort to relax a lot of these restrictions where possible.
In the new version some of these limitations have been lifted, so for example
{env:...} can be used in install stanzas
(#10160).
Likewise there was no consistency where %{cma:...} or %{cmo:...} could be
used. With #10169, these forms
should work consistently everywhere.
Similarly the variables allowed in enabled_if fields have been expanded in
#10250, from just allowing
variables that can be computed from the context to now allowing all variables
as long as expanding these variables does not introduce dependency cycles.
These relaxed rules can also be combined to enable a library depending on
environment variables, e.g. (enabled_if %{env:ENABLE_LIBFOO=false})).
Continuing the theme of conditionally enabling or disabling code to be built,
@jchavarri and @rgrinberg's work on
#10220 makes it possible to have
overlapping names between executable and melange.emit targets. This can be
useful when a name is to be shared in different contexts (e.g. one context with
native compilation and one emitting code for the browser).
Dune does not assume an encoding of dune files, however when files were formatted the formatter would err on the safe side and escape bytes outside the ASCII range. This means that UTF-8 characters outside of ASCII would get escaped into decimal escape sequences.
This was especially annoying in places where the user would write natural
language texts, which is common when defining Opam packages in dune-project
files. For example a discussion of a paper by Paul Erdős, Peter Frankl, Vojtěch
Rödl would upon reformatting be turned into Paul Erd\197\145s, Peter Frankl,
Vojt\196\155 R\195\182, which does a disservice to these scientists and is
hard to read.
Thanks to the work of @moyodiallo in #9728 starting with Dune 3.15 the original encoding will be preserved, so your package descriptions will be more readable.
Add link flags to to ocamlmklib for ctypes stubs (#8784, @frejsoya)
Remove some unnecessary limitations in the expansions of percent forms in
install stanza. For example, the %{env:..} form can be used to select files
to be installed. (#10160, @rgrinberg)
Allow artifact expansion percent forms (%{cma:..}, %{cmo:..}, etc.) in
more contexts. Previously, they would be randomly forbidden in some fields.
(#10169, @rgrinberg)
Allow %{inline_tests} in more contexts (#10191, @rgrinberg)
Remove limitations on percent forms in the (enabled_if ..) field of
libraries (#10250, @rgrinberg)
Support dialects in dune describe pp (#10283, @emillon)
Allow defining executables or melange emit stanzas with the same name in the same folder under different contexts. (#10220, @rgrinberg, @jchavarri)
coq: Delay Coq rule setup checks so OCaml-only packages can build in hybrid
Coq/OCaml projects when coqc is not present. Thanks to @vzaliva for the
test case and report (#9845, fixes #9818, @rgrinberg, @ejgallego)
Fix conditional source selection with select on bigarray in OCaml 5
(#10011, @moyodiallo)
melange: fix inconsistency in virtual library implementation. Concrete modules within a virtual library can now refer to its virtual modules too (#10051, fixes #7104, @anmonteiro)
melange: fix a bug that would cause stale import paths to be emitted when
moving source files within (include_subdirs ..) (#10286, fixes #9190,
@anmonteiro)
Dune file formatting: output utf8 if input is correctly encoded (#10113, fixes #9728, @moyodiallo)
Fix expanding dependencies and locks specified in the cram stanza. Previously, they would be installed in the context of the cram test, rather than the cram stanza itself (#10165, @rgrinberg)
Fix bug with dune exec --watch where the working directory would always be
set to the project root rather than the directory where the command was run
(#10262, @gridbugs)
Regression fix: sign executables that are promoted into the source tree (#10263, fixes #9272, @emillon)
Fix crash when decoding dune-package for libraries with (include_subdirs qualified) (#10269, fixes #10264, @emillon)
--react-to-insignificant-changes option. (#10083, @rgrinberg)We are happy to announce the release of MDX 2.4.0! This is the first release of MDX to be compatible with OCaml 5.2.
This release also comes with support for executing included OCaml code blocks.
skip to include blocks
to revert to the old behavior (#446, @panglesd, @gpetiot)
Warning: this is a breaking change that is reverted in the next release.We're happy to announce that Dune 3.14.2 is now available.
Note that due to a regression that was detected before publishing to opam
version 3.14.1 should not be used. The fix for the regression is part of
this release.
This feature brings some small bugfixes around the handling of Coq as well as solves an issue where Dune is running on Windows in a path that contains Unicode characters. This affected e.g. users with diacritics or non-latin script in their name when running Dune within their home directory.
When a directory is changed to a file, correctly remove it in subsequent
dune build runs. (#9327, fix #6575, @emillon)
Fix a problem with the doc-new target where transitive dependencies were missed during compile. This leads to missing expansions in the output docs. (#9955, @jonludlam)
coq: fix performance regression in coqdep unescaping (#10115, fixes #10088, @ejgallego, thanks to Dan Christensen for the report)
coq: memoize coqdep parsing, this will reduce build times for Coq users, in particular for those with many .v files (#10116, @ejgallego, see also #10088)
on Windows, use an unicode-aware version of CreateProcess to avoid crashes
when paths contains non-ascii characters. (#10212, fixes #10180, @emillon)
fix compilation on non-glibc systems due to signal.h not being pulled in
spawn stubs. (#10256, @emillon)
This release of UTop 2.14.0 brings support for the upcoming version of the compiler, OCaml 5.2.
We're thrilled to announce the release of Merlin 4.14, a significant update that introduces a suite of enhancements and fixes to improve your OCaml editor experience.
In addition to the improvements and bug fixes in this release, Merlin 4.14 is the first version to support the upcoming OCaml 5.2 compiler.
Some highlights in this release include:
Happy coding!
FLG -pp ppx.exe -as-pp/-dump-ast use of invalid shell redirection when
direct process launch on Windows. (#1723, fixes #1722)ocamlmerlin responses to detect server crashes (#1716)module-type (#1728, partially fixes #1656)We're happy to announce that Dune 3.14.0 is now available. This feature has many fixes and new features that you can find in the changelog.
There are a few new features that we would like to specially highlight.
(dynamic_include)It is common for some parts of a build to be dynamic: for example a source file can be generated, or some parts of the configuration like C flags can be generated from a Dune rule. But until now it was not possible to generate rules dynamically.
For example, one might want to do it is to set up one rule per input file. This is a common pattern in test suites and is easy to do with Make. But Dune does not have a concept of parameterized rules, so it is necessary to set up one rule per input file.
The pattern to do this with Dune is to:
dune.inc file using this generator;(include dune.inc) in the main dune file,However, this requires checking in the generated dune.inc file in the
repository. Another drawback is that when modifying the list of input files, it
is necessary to run tests twice: one to update dune.inc, one to run the new
test.
This release of Dune adds a new (dynamic_include) stanza that lifts these
restrictions: dune.inc does not have to be part of the source tree, it can be
generated transparently. This comes with some restrictions: some stanzas can
not be generated, in particular the ones that define public libraries. And due
to how rule loading works, the generated stanza needs to be defined in a
different directory.
Still, this should be useful for many users that rely on the generate-include-commit pattern described above.
Sherlodoc is a search engine for OCaml documentation, which supports search by
name, documentation and fuzzy type search (similar to Hoogle in the Haskell
world). It can be obtained from opam using opam install sherlodoc.
When it is available, Dune commands that produce HTML documentation, such as
dune build @doc and dune build @doc-new, will include a search bar in the
generated output.
Introduce a (dynamic_include ..) stanza. This is like (include foo) but
allows foo to be the target of a rule. Currently, there are some
limitations on the stanzas that can be generated. For example, public
executables, libraries are currently forbidden. (#9913, @rgrinberg)
Introduce $ dune promotion list to print the list of available promotions.
(#9705, @moyodiallo)
If Sherlodoc is installed, add a search bar in generated HTML docs (#9772, @EmileTrotignon)
Add only_sources field to copy_files stanza (#9827, fixes #9709,
@jchavarri)
The (foreign_library) stanza now supports the (enabled_if) field. (#9914,
@nojb)
Fix $ dune install -p incorrectly recognizing packages that are supposed to
be filtered (#9879, fixes #4814, @rgrinberg)
subst: correctly handle opam files in opam/ subdirectory (#9895, fixes #9862, @emillon)
Odoc private rules are not set up if a library is not available due to
enabled_if (#9897, @rgrinberg and @jchavarri)
When dune language 3.14 is enabled, resolve the binary in (run %{bin:..} ..) from where the binary is built. (#9708, @rgrinberg)
boot: remove single-command bootstrap. This was an alternative bootstrap strategy that was used in certain conditions. Removal makes the bootstrap a bit slower on Linux when only a single core is available, but bootstrap is now reproducible in all cases. (#9735, fixes #9507, @emillon)
The ppxlib dev team is happy to announce the release of ppxlib.0.32.0.
The main feature of this release, implemented by @burnleydev1 during their Outreachy internship, is a huge improvement of the handling of located exceptions raised by ppx-es. Whenever a rewrite of the AST throws such an exception, the ppxlib driver catches it and resumes the rewriting using the latest valid AST it knows of. All caught exceptions are appended to the final AST as [%%ocaml.error ..] nodes. This means the driver returns a valid AST instead of one composed of a single error node corresponding to the first raised exception.
This leads to a much better experience for ppx users as merlin now has a valid AST to work with when this happens, allowing it to properly function, reporting all errors, from ppx-es or otherwise.
Note that despite this change we still recommend ppx authors to embed errors in the rewritten AST rather than throw exceptions.
The release also comes with a few bug fixes on longident parsing or windows compatibility and a new simplified API for ppx authors using attributes as flags (i.e. attributes without payloads such as [@ignore] for instance).
We'd like to thank our external contributors for this release:
We'd also like to thank the OCaml Software Foundation who has been funding my work on this release.
Add an optional embed_errors argument to Context_free.map_top_down that
controls how to deal with exceptions thrown by context-free rules.
(#468, @NathanReb)
Fix Longident.parse so it properly handles unparenthesized dotted operators
such as +. or *.. (#111, @rgrinberg, @NathanReb)
raising an exception does no longer cancel the whole context free phase(#453, @burnleydev1)
Sort embedded errors that are appended to the AST by location so the compiler reports the one closer to the beginning of the file first. (#463, @NathanReb)
Update Attribute.get to ignore loc_ghost. (#460, @ceastlund)
Add API to manipulate attributes that are used as flags (#408, @dianaoigo)
Update changelog to use ISO 8061 date format: YYYY-MM-DD. (#445, @ceastlund)
Replace Caml with Stdlib. (#427, @ceastlund)
When a transformation raises, the last valid AST is used as input to the upcoming transformations. All such errors are collected and appended as extension nodes to the final AST (#447, @burnleydev1)
Fix a small mistake in the man pages: Embededding errors is done by default with
-as-pp, not with -dump-ast (#464, @pitag-ha)
Set appropriate binary mode when writing to stdout especially for Windows
compatibility. (#466, @jonahbeckford)
We just released version 3.13.1 with some bugfixes.
Fix performance regression for incremental builds (#9769, fixes #9738, @rgrinberg)
Fix dune ocaml top-module to correctly handle absolute paths. (#8249, fixes
#7370, @Alizter)
subst: ignore broken symlinks when looking at source files (#9810, fixes #9593, @emillon)
subst: do not fail on 32-bit systems when large files are encountered. Just log a warning in this case. (#9811, fixes #9538, @emillon)
boot: sort directory entries in readdir. This makes the dune binary reproducible in terms of filesystem order. (#9861, fixes #9794, @emillon)
The release of odoc 2.4.0 last month introduced a regression that caused Dune rules to fail in some cases. This release of odoc 2.4.1 fixes this issue.
We're happy to announce that Dune 3.13.0 is now available. This feature is packed with fixes and new features that you can find in the changelog.
There are a few new features that we would like to specially highlight.
When menhir is used to generate code from .mly files, there are sometimes
issues with the grammar itself, such as shift-reduce conflicts.
Menhir has an option to generate a "conflicts" file using its --explain flag,
but until now this was not exposed by Dune. Starting from this version, this
file will be generated automatically to help developers debug their grammars.
Dune's global cache is a way to save the result of intermediate build results, even across projects. Previously, it would only work with file targets. With this change, it now supports Dune's experimental directory targets.
In several places in the Dune language, it is possible to pass a list of
modules. For example in a (library) stanza, if for some reason the default of
picking all the source files in the current directory is not the right thing to
do, it is possible to pass (module A B C) to only attach these modules to the
library.
An important limitation has been that the list of modules needed to be static:
written as is in the dune file. This limitation has now been lifted and it is
possible to use (:include) or %{read-lines:file} in this field and similar
ones.
LexiFi's use case is a system of static plug-ins: a program is extended by selecting which modules are linked to the application core. This list of modules can now be emitted by a generator that reads a configuration file.
Previously, this required using OCaml syntax for the dune file, which has
several issues, including incompatibility with features like
(include_subdirs) and poor performance because Dune does not know the
dependencies of the generator and needs to re-run the build more times than
necessary.
Add command dune cache clear to completely delete all traces of the Dune
cache. (#8975, @nojb)
Allow to disable Coq 0.8 deprecation warning (#9439, @ejgallego)
Allow OCAMLFIND_TOOLCHAIN to be set per context in the workspace file
through the env stanza. (#9449, @rgrinberg)
Menhir: generate .conflicts file by default. Add new field to the
(menhir) stanza to control the generation of this file: (explain <blang expression>). Introduce (menhir (flags ...) (explain ...)) field in the
(env) stanza, delete (menhir_flags) field. All changes are guarded under
a new version of the Menhir extension, 3.0. (#9512, @nojb)
Directory targets can now be cached. (#9535, @rleshchinskiy)
It is now possible to use special forms such as (:include) and variables
%{read-lines:} in (modules) and similar fields. Note that the
dependencies introduced in this way (i.e., the files being read) must live in a
different directory than the stanza making use of them. (#9578, @nojb)
Remove warning 30 from default set for projects where dune lang is at least
3.13 (#9568, @gasche)
Add coqdoc_flags field to coq field of env stanza, allowing the setting
of workspace-wide defaults for coqdoc_flags. (#9280, fixes #9139, @Alizter)
ctypes: fix an error where (ctypes) with no (function_description) would
cause an error trying refer to a nonexistent _stubs.a dependency (#9302,
fix #9300, @emillon)
(depends) and related fields in dune-project
are well-formed. (#9472, fixes #9270, @ElectreAAS)Do not ignore (formatting ..) settings in context or workspace files
(#8447, @rgrinberg)
Fixed a bug where Dune was incorrectly parsing the output of coqdep when it was escaped, as is the case on Windows. (#9231, fixes #9218, @Alizter)
Copying mode for sandboxes will now follow symbolic links (#9282, @rgrinberg)
Forbid the empty (binaries ..) field in the env stanza in the workspace
file unless language version is at least 3.2. (#9309, @rgrinberg)
[Coq] Fix bug in computation of flags when composed with boot theories. (#9347, fixes #7909, @ejgallego)
Fixed a bug where the (select) field of the (libraries) field of the
(test) stanza wasn't working properly. (#9387, fixes #9365, @Alizter)
Fix handling of the PATH argument to dune init proj NAME PATH. An
intermediate directory called NAME is no longer created if PATH is
supplied, so dune init proj my_project . will now initialize a project in
the current working directory. (#9447, fixes #9209, @shonfeder)
Experimental doc rules: Correctly handle the case when a package depends upon its own sublibraries (#9461, fixes #9456, @jonludlam)
Resolve various public binaries to their build location, rather than to where
they're copied in the _build/install directory (#9496, fixes #7908,
@rgrinberg).
Correctly ignore warning flags in vendored projects (#9515, @rgrinberg)
Use watch exclusions in watch mode on MacOS (#9643, fixes #9517, @PoorlyDefinedBehaviour)
Fix Merlin configuration for (include_subdirs qualified) modules (#9659,
fixes #8297, @rgrinberg)
Fix handling of enabled_if in binary install stanzas. Previously, we'd
ignore the result of enabled_if when evaluating %{bin:..} (#9707,
@rgrinberg)
We just released version 3.12.2 with 2 bugfixes.
Fix version check in runtest_alias for cram stanza (#9454, @emillon)
Fix stack overflow when a (run) action can not be parsed. (#9530, fixes
#9529, @gridbugs)
We are pleased to announce the release of OCaml LSP 1.17.0. This version comes packed with fixes and new features.
Notable features that come in this release include:
in keyword completing to other terms in the editor, we've added auto-completion for this keyword in OCaml LSP. Typing in will now only suggest auto completion for the in keyword.--fallback-read-dot-merlin flag is on. (#1173)in (#1217)The odoc team is delighted to announce the release of odoc 2.4.0. It mainly contains support for search engines. There are of course bugfixes and smaller new features.
Odoc now support searching in the documentation ! The search is made to run in the browser, so that you do not need a server to enable search: you can have search on your documentation hosted on github pages or even locally on your machine.
No search engine is shipped with, you need to provide one, but all the facilities to make use of one are present. We adapted @art-w 's sherlodoc for seamless integration with odoc, alongside with new features. It is not yet released on opam, but we hope it will be soon.
You can already test sherlodoc and play with it on your own projects, there are instructions in its readme. Sherlodoc has fuzzy typed-based search like hoogle in the haskell world, and is made to work best for OCaml (unlike a general purpose search engine like elastic search).
Check the results on odoc's own online documentation : ocaml.github.io/odoc.
While we are dedicated to developing the best tooling to generate and serve documentation on OCaml.org, creating a well-documented library ecosystem can only be a collective effort. Package authors: we’re working hard to give you great tools, but we’ll need all your help to create an ecosystem of well-documented libraries for OCaml!
If you find that writing documentation for your library isn’t as straightforward as you would like, please do share your feedback with us.
We're happy to announce the release of Merlin 4.13. This release comes with a number of bug fixes to the Merlin binary.
It also introduces a new -cache-lifespan flag that can be used to set cache invalidation periods. This flag allows for fine-tuning of cache invalidation periods, enabling users to customize Merlin's internal configurations for optimal performance in various project contexts.
Additionally, this release includes several improvements in editor modes. For more details, we encourage you to delve into the full changelog.
-cache-lifespan flag, that sets cache invalidation period. (#1698,
#1705)