OCaml Weekly News

Hello

Here is the latest OCaml Weekly News, for the week of September 17 to 24, 2= 024.

ocaml-trace 0.8

Archive: https://discuss.ocaml.org/t/ann-ocaml-trace-0-8/15298/1

Simon Cruanes announced

ocaml-t= race 0.8 was just released. It features a new trace collector for multi= process programs, and a new library, trace.subscriber, for han= dling events in a more modular, compositional way.

For background, trace is a lightweight library that can be use= d to instrument your code (libraries or executable), either by hand or usin= g ppx_trace, and offers a collector abstraction t= o actually collect/handle/store/write the trace events somewhere. The overh= ead when no collector is installed is low. There are also several collector= s in trace-tef, trace-fuchsia, and (in a separate= repo) tracy-client. See the github repo for more details.

qcheck-lin and qcheck-stm 0.2

Archive: https://discuss.ocaml.org/t/ann-qcheck-lin-and-qcheck-stm-0= -2/12301/3

Jan Midtgaard announced

I'm happy to share the 0.4 release of qcheck-lin, qcheck= -stm, and qcheck-multicoretests-util: https://githu= b.com/ocaml-multicore/multicoretests/releases/tag/0.4

The testing libraries are useful for testing your OCaml code for parallelis= m safety:

qcheck-lin offer a low effort approach, requiring little m= ore than type signatures of the target interface (example above)
qcheck-stm offers stronger correctness guarantees by compa= ring the observed behaviour to a functional model description - under both = sequential and parallel usage.

The 0.4 release brings two new "stress test" functions and also adjusts the= cmd list distribution of STM_sequential:

#415: Remove --verbose in internal mutable_set_v5 expect test to avoid a test failure on a slow machine


#443: Add Lin_domain.stress_test as a lighter stress test,=
 not requiring an interleaving search.
#462: Add STM_domain.stress_test_par, similar to Lin=
_domain.stress_test for STM models.
#472: Switch arb_cmds to use an exponential distribution w=
ith a mean of 10, avoiding lists of up to 10000 cmds in STM_sequentia=
l (reported by @nikolaushuber).




Happy testing! :smiley:







3rd editor tooling dev-meeting: 26th of September =F0=9F=A7=99=



Archive: https://discuss.ocaml.org/t/ann-3rd-edit=
or-tooling-dev-meeting-26th-of-september/15308/1




vds announced


The meeting is back! We are organizing the next one on next Thursday, the 2=
6th of September at 5pm CEST (sorry, still no timezone rotation, but we pro=
bably will for the next one). Whether you are a long time maintainer, an oc=
casional contributor, a new comer, or simply a curious passer-by, please fe=
el free to attend!=20



:sparkles: For this session, @jchavarri is going to present Melange, a toolchain that compiles o=
caml/reason to javascript,  and its integration in the tooling ecosystem.



:clipboard: Meeting agenda:



A tour-de-table to allow the participants that wish to do so to present=
 themselves and mention issues / prs they are interested in.
Talk and Q&A
Discuss issues and pull requests that were tagged in advance or mention=
ed during the tour-de-table.



We=E2=80=99re looking forward to meeting you!



Meeting link: https://meet=
.google.com/nzt-owbh-yoo 



Previous meeting notes are available in Merlin=E2=80=99s repository wiki<=
/a>.









First release of hachis


Archive: https://discuss.ocaml.org/t/ann-first-release-of-hachis/15309/1




Fran=C3=A7ois Pottier announced


It is my pleasure to announce the first release of hachis, a l=
ibrary that offers hash sets and hash maps.



These data structures handle collisions via linear probing, a technique tha=
t relies on linear searches within an array. All of the data is stored with=
in one large array (for hash sets) or two large arrays (for hash maps). As =
a result, these data structures offer good locality.



Some benchmarks suggest that hachis can consistently outperfor=
m the standard library's hash maps (Hashtbl).



To install the library, type opam update && opam install hach=
is.



For more details, see the documentation.






Simon Cruanes then added


The code is here for tho=
se who are
curious to see how the sausage is done :-)


OCaml Platform Newsletter: June-August 2024


Archive: https://discuss.ocaml.org/t/ocaml-platform-newslet=
ter-june-august-2024/15312/1


Thibaut Mattio announced


Welcome to the twelfth edition of the OCaml Platform newsletter!



In this June-August 2024 edition, we are excited to bring you the latest on=
 the OCaml Platform, continuing our tradition of highlighting recent develo=
pments as seen in previous editions. To understand the direction we're headed, espec=
ially regarding development workflows and user experience improvements, che=
ck out our roadmap.



Highlights:



Dune package management soon in public beta: Developer Pre=
view Program expands with 60+ interviews, NPS soaring from +9 to +28! P=
ublic beta coming soon with exciting features like automatic dependency loc=
king and dev tool management. See it in action!
Opam 2.2 is out: Native Windows support is here! Seamless setup wit=
h opam init, opam-repository compatible with Wind=
ows. OCaml on Windows is now a reality.
Odoc 3.0 gets close to a release: New features like global sideb=
ars and media support are ready in odoc. Integration with Dune and OCaml.or=
g pipeline in progress - get ready to test the new documentation experience=
 soon! Check out=
 the RFCs.
Project-wide references is live: Merlin 5.1 and OCaml LSP 1.18.0=
 bring powerful code navigation to your editor. Built on years of compiler =
work, it's a game-changer for large codebases.
Starting to bridge the gap between Merlin and OCaml LSP: New LSP=
 queries for type enclosing, documentation, and more. We=E2=80=99re working=
 towards consistent, feature-rich experience across all editors powered by =
OCaml LSP.



Releases:



opa=
m 2.2.0~beta3
opam =
2.2.0~rc1
opam 2.2.=
0
opam 2.2.=
1
Dune 3.1=
6.0
opam-publish 2.3.1
Merlin 5.=
1
Merlin 4=
.16
Merlin =
4.15
OCa=
ml LSP 1.19.0
OCa=
ml LSP 1.18.0
Ppxlib=
 0.33.0


Dune Package Management (W4)



Contributed by: @rgrinberg (Tarides), @Leonidas-from-XIV (Tarides), =
@gridbugs (Tarides), @Alizter



Synopsis: Integrating package management into Dune, making it the so=
le tool needed for OCaml development. This unification eliminates installat=
ion time (just download Dune's pre-built binary), automates external tool m=
anagement (e.g., for dune fmt or dune ocamllsp), =
and significantly reduces build times through caching (packages and compile=
r are built only once across projects).



Summary:



Following our announcement of reaching the Minimal Viable Product (MVP) sta=
ge for Dune's package management in the last newsletter, we=
've made substantial progress on our stated goals. As promised, we've shift=
ed our focus from prototyping to user testing and refining the developer ex=
perience (DX).



The Developer Preview Program (see latest update) has expanded si=
gnificantly from its early stages. We've conducted approximately 60 develop=
er interviews, representing a diverse cross-section of the OCaml community.=
 The interviewees include both newcomers and experienced OCaml users. Notab=
ly, about 40% of participants have over 3 years of OCaml experience, while =
35% are relative newcomers with less than a year of experience. The majorit=
y come from Linux and macOS environments, with participants representing va=
rious sectors including tech companies, research institutions, and independ=
ent developers.



These sessions have provided crucial feedback and driven improvements. This=
 extensive user testing has paid off, with the Net Promoter Score jumping f=
rom +9 to an estimated +28 - a clear sign that the community is excited abo=
ut the improvements we've made.



Key developments since the last update include:


A nightly binary distribution of Dune with package management enabled, =
which will be made available publicly in the coming weeks.

We started work on automated handling of developer tools (ocamlformat, = ocamllsp, odoc) – users will be able run dune fmt, or <= code>dune ocamllsp, and Dune will take care of installing OCamlForma= t and OCaml LSP automatically if they are not available.
Implementation of automatic dependency locking when project=E2=80=99s d= ependency changes – you can now run Dune in watch mode and let it in= stall your dependencies without any intervention after updating your dune-p= roject
We=E2=80=99ve enabled Dune cache by default, which works with your pack= age dependencies. With this change, Dune will not recompile dependencies mo= re than once when building new projects, including the compiler!

The team has moved beyond just testing with OCaml.org and Bonsai, now condu= cting broader compatibility tests across the opam repository. Initial resul= ts show about 50% of packages can be authored using Dune with package manag= ement, with ongoing efforts to increase the coverage (we expect resolution = of a few issues on a select few foundational packages to significantly incr= ease that percentage).

In line with the commitment to prepare for a first release, the team plans = to launch a public beta in the coming weeks. This marks a significant step = from our current private Developer Preview testing with selected beta teste= rs, to a broader community release.

Stay tuned for the upcoming announcement, and in the meantime, have a look = a the demos and some enthusiastic messages from beta testers:

Demo on Ma= stodon or X
=E2=80=9CJust did the dune package management preview, it=E2=80=99s loo= king very sharp=E2=80=9D – https://x.com/ckarmstrong/status/183093715643474756= 6
=E2=80=9CReally looking forward to this! No more switches, no more opam= , just dune behaving like a modern package manager. Having played around wi= th it, it's just so so nice. The focus on DX really makes me hopeful about = OCaml's future.=E2=80=9D – https://x.com/synecdokey/status/1825533523283079474<= /a>

Activities:

Implemented workaround to avoid unstable compilers – ocaml/dune#10668
Added support for multiple checksums (ocaml/dune#10624, ocaml/dune#10791)
Began upstreaming the Dune toolchain feature (ocaml/dune#10639, ocaml/dune#10719)
Added implicit relock when dependencies change – ocaml/dune#10641
Improved dependency solving and constraint handling (ocaml/dune#10726)
Added developer preview features and configuration options (ocaml/dune#10627)
Implemented progress indicators for package builds and lockfile generat= ion (ocaml/dune#10802<= /a>, ocaml/dune#10803<= /a>)

Improved error messages and logging (ocaml/dune#10662)
Created extensive test suite for new package management features (ocaml/dune#10798)
Resolved issues with building specific packages (e.g., seq, lwt) (ocaml/dune#10788, ocaml/dune#10839)
Enable cache on fetch actions for faster builds (ocaml/dune#10850)
Improved handling of dev tools like ocamlformat (ocaml/dune#10647)
Developed tools for testing package compatibility coverage on opam-repo= sitory

Native Support for Windows in opam 2.2 (W5)

Contributed by: @rjbou (OCamlPro), @kit-ty-kate (Ahrefs), @dra27 (Ta= rides), @AltGr (OCamlPro)

Synopsis: Releasing opam 2.2 with native Windows support to enhance = OCaml's viability on Windows, making the official opam-repository usable on Windows and encouraging more Windows-friendly packages.
Summary: The release of opam 2.2.0, announced on Discuss early July, marks a significan= t milestone for the OCaml ecosystem. This version brings native support for= both the opam client and compiler packages in opam-repository= on Windows, opening new possibilities for OCaml development on this platfo= rm. opam 2.2.0 officially supports Cygwin and is compatible with MSYS2. Windows= users can now run opam init in their preferred console for a = guided setup, resulting in a fully functional OCaml environment. This relea= se represents the culmination of a multi-year effort involving extens= ive contributions from the community. The OCaml ecosystem is already adapting to this new capability. A CI check for Windo= ws compilation has been added to opam-repository, and the GitHub Action ocaml= /setup-ocaml now uses opam 2.2.0, facilitating OCaml development on Win= dows in GitHub projects. Community members are actively working to improve Windows compatibility acr= oss the ecosystem. Notable efforts include Hugo Heuzard's work on OCamlBuild and several other Windows-related PRs. We encourage package authors to set up Windows CI for their projects and ad= dress Windows-related issues. This collective effort will be crucial in exp= anding OCaml's reach and usability on the Windows platform. Activities: Opam binary: Fixed issues with opam init on Windows – ocaml/opam#5991, ocaml/opam#5992, ocaml/opam#5993, ocaml/opam#5994, ocaml/opam#5995, ocaml/opam#5996, ocaml/opam#5997, ocaml/opam#5998, ocaml/opam#6000 Improved status display during slow operations on Windows – ocaml/opam#5977 Enabled opam to work with Windows usernames containing spaces – = ocaml/opam#5457 Fixed opam init -yn to handle menus in the release candida= te – ocaml/opam#= 6033 Updated PowerShell script for installing opam from GitHub releases: ocaml/opam#5906 Fixed hang issue with setup-ocaml and depexts – ocaml/opam#6046 Update opam-repository to be compatible with Windows: Updated opam-repository Windows CI – ocaml/opam-repository#260= 81, oca= ml/opam-repository#26073, ocaml/opam-repository#26080 Added backport of MSVC in OCaml-variants.5.2.0+msvc – ocaml/opam-repository= #26082 Updated native Cygwin depexts – ocaml/opam-repository#26130 Updated opam-repository with Windows-specific package information: Added Windows compiler packages (ocaml/opam-repository#25861) Fixed issues with OCaml variants on Windows (ocaml/opam-repository#26033) Updated and released mingw-w64-shims.0.2.0 to fix setup-ocaml issues (<= a href=3D"https://github.com/ocaml/opam-repository/pull/26123">ocaml/opam-r= epository#26123) Released stable version of opam 2.2.0 with full Windows support =F0=9F= =8E=89 (announcement)

Upgrading OCaml Package Documentation with Odoc 3.= 0 (W25) Contributed by: @jonludlam (Tarides), @julow (Tarides), @panglesd (T= arides), @EmileTrotignon (Tarides), Luke Maurer (Jane Street) Synopsis: Upgrading OCaml package documentation experience with odoc= 3, featuring improved navigation, cross-package referencing, media support= , and more. This upgrade aims to improve the documentation experience both = locally and on OCaml.org, encouraging higher-quality package documentation. Summary: Following the completion and community review of the RFCs for odoc 3.0, we'= ve made significant strides in implementing the new design and features. Ou= r progress over the past few months has brought us close to a complete impl= ementation of the odoc 3.0 feature set. As we finalize development and appr= oach the first release, our focus is shifting towards integration with the = rest of the ecosystem. Key Developments in the past months include: Adding new options to the odoc CLI to begin the implementa= tion of the odoc 3 CLI Implementing new syntax such as path-references Developing the global sidebar with a TOC featuring standalone pages and= package module hierarchy As we near completion of the core odoc 3.0 feature set, our focus is shifti= ng towards finalizing integration with Dune and the OCaml.org documentation= pipeline. We're excited to get all of these improvements in your hands and= get your feedback on the new documentation experience. Stay tuned for anno= uncements regarding testing opportunities and the upcoming release of odoc = 3.0! Activities: Added path-references lookup functionality – ocaml/odoc#1150 Added the --current-package option – ocaml/odoc#1151 Fixed hierarchical pages being given wrong parent ID – ocaml/odoc#1148 Parsing of path-references to pages and modules (ocaml/odoc#1142) Support for assets and media in documentation (ocaml/odoc#1184) Implemented "Global" sidebar feature (ocaml/odoc#1145) Added support for external pages and non-package documentation (ocaml/odoc#1183) Improved CSS for better visual presentation (ocaml/odoc#1159) Add a marshalled output for index generation (ocaml/odoc#1084) Implemented Voodoo/Dune driver for improved integration (ocaml/odoc#1168) Added frontmatter support to mld pages (ocaml/odoc#1187) Improved breadcrumbs to show packages and libraries (ocaml/odoc#1190) Project-Wide References in OCaml Editors (W19)= Contributed by: @vds (Tarides) Synopsis: Introducing project-wide reference features in Merlin and = OCaml LSP to enhance code navigation and refactoring capabilities, bringing= OCaml's editor experience in line with other modern programming languages. Summary: As announced in June, Merlin project-wide references = is now available in Merlin 5.1 and the preview of OCaml LSP 1.18.0. Users o= f LSP-powered editors (like VSCode with the OCaml Platform extension) and c= lassic Emacs and Vim plugins can now query project-wide references of OCaml= terms. This requires building the index with the new Dune alias @oca= ml-index. This release represents the culmination of a multiyear effort by the Merlin= team, including extensive work on the compiler to provide the necessary in= formation for implementing this feature in Merlin. We're thrilled to share this feature with the community and look forward to= your feedback. While the feature should work well in most cases, we're aware of some limit= ations. Our next steps include adding support for interface files and modul= e paths. Stay tuned! Activities: Completed work on incremental occurrences indexation and related Dune r= ules – ocaml/du= ne#10422 Fixed issues with querying from interface files – ocaml/merlin#1779, ocaml/merlin#1781 Improved behavior when cursor is on label/constructor declarations = 013; ocaml/merlin#178= 5 Released Merlin.5.1-502, ocaml-index.1.0, and= a new preview of ocaml-lsp-server with project-wide occurrenc= es support – ocaml/opam-repository#26114 Announced the release on Discuss – Project-wid= e occurrences in Merlin and LSP Wrote a wiki page for project-wide occurrences Updated the Merlin website Updated the pl= atform changelog Improved handling of label and constructor declarations (ocaml/merlin#1785) Contributed compiler improvements: Implemented distinct unique identifiers for implementations and interfa= ces (ocaml/ocaml#1328= 6) Developed a system for linking unique identifiers of declarations (ocaml/ocaml#13308) Contributed to improvements in longident locations (ocaml/ocaml#13302)
Bridging the Gap Between Merlin and OCaml LSP (W19)=
Contributed by: @xvw (Tarides), @vds (Tarides) Synopsis: Working towards feature parity between Merlin and OCaml LS= P to provide a consistent, feature-rich development experience across all e= ditors, making OCaml LSP the comprehensive backend for OCaml editor support. Summary: In June, we started work on bridging the gap between OCaml LSP and Merlin. = We've started with exposing Merlin's type-enclosing request in OCaml LSP. T= he feature is now available as ocamllsp/typeEnclosing and we w= ill work on editor integration next. As a reminder, Merlin's type-enclosing feature allows users to= get the type of the identifier under the cursor. It highlights the identif= ier and displays its type. Users can climb the typed-tree to display the ty= pe of larger expressions surrounding the cursor. Since June, we=E2=80=99ve worked on a number of new LSP queries and code ac= tions, including:
A custom ocamllsp/getDocumentation query to request the odoc documentation

A custom ocamllsp/construct query to browse and fill typed= holes (_)

A code-action for syntactic and semantic movement shortcuts based on Me= rlin's Jump command

Activities

Added custom queries for type enclosing and documentation retrieval:

Type enclosing query (ocaml/ocaml-lsp#1304)

Documentation query (ocaml/ocaml-lsp#1336)

Created a custom construct query (ocaml/ocaml-lsp#1348)

Implemented semantic and syntactic movement shortcuts (ocaml/ocaml-lsp#1364)

Backported and released Merlin 4.16 with necessary commands (opam-repository PR)

Refactored usage of Typedtree from ocaml-lsp = to merlin-lib (ocaml/merlin#1811, ocaml/merlin#1812)

First alpha release of OCaml 5.3.0

Archive: https://discuss.ocaml.org/t/first-alpha-release-of-ocaml-5= -3-0/15315/1

octachron announced

Four months after the release of OCaml 5.2.0, the set of new features for t= he future version 5.3.0 of OCaml has been frozen. We are thus happy to anno= unce the first alpha release for OCaml 5.3.0.

This alpha version is here to help fellow hackers join us early in our bug = hunting and opam ecosystem fixing fun (see below for the installation instr= uctions). More information about the whole release process is now available= in the compiler repository.

The progresses on stabilizing the ecosystem are tracked on the opam readiness for 5.= 3.0 meta-issue.

The full release is expected around November, see the new prospective c= alendar for more information.

If you find any bugs, please report them on OCaml's issue tracker.

If you are interested in the ongoing list of new features and bug fixes, th= e updated change log for OCaml 5.3.0 is available on GitHub.

Installation Instructions

The base compiler can be installed as an opam switch with the following com= mands on opam 2.1 and later:

opam update opam switch create 5.3.0~alpha1

The source code for the alpha is also available at these addresses:

= GitHub

OCaml archives at Inria

Fine-Tuned Compiler Configuration

If you want to tweak the configuration of the compiler, you can switch to t= he option variant with:

opam update opam switch create <switch_name> ocaml-variants.5.3.0~alpha1+options = <option_list>

where option_list is a space separated list of ocaml-opt= ion-* packages. For instance, for a flambda and no-flat-float-array = switch:

opam switch create 5.3.0~alpha1+flambda+nffa ocaml-variants.5.3.0~alpha1+op= tions ocaml-option-flambda ocaml-option-no-flat-float-array

All available options can be listed with opam search ocaml-option.
Ascend - Dungeon RPG for your terminal Archive: https://discuss.ocaml.org/t/ann-ascend-dungeon-rpg-f= or-your-terminal/15319/1 eir announced Announcing the first release of ascend! Venture into the depths to retrieve the stolen artifact, and hopefully esca= pe with your life… NetHack lite. Get it via: opam install ascend ascend Rievax the Revelator is recruiting you for some "manual testing". first release of ppx_deriving_jsonschema Archive: https://discuss.ocaml.org/t/ann-first-release-of= -ppx-deriving-jsonschema/15320/1 Louis Roch=C3=A9 announced It is my pleasure to announce the first release of ppx_deriving_jsonschema. Source = repo is http= s://github.com/ahrefs/ppx_deriving_jsonschema/ This small ppx should help you generate a (hopefully valid) json schema fro= m an ocaml type.=20 Generally the derivation tries to produce a schema which looks natural, and= that would also be compatible with the existing derivers for json out ther= e. Basically you should be able to change the annotation to [@@derivi= ng jsonschema, yojson] (or json instead of yojson= ) and to read/write json values that are matching the schema. There = is a bit of tension on things like variants, which are represented as array= s by ppx_yojson_conv and ppx_deriving_yojson, but represented as enums by p= px_deriving_jsonschema. I plan to add a way to switch between the two behav= iors soon. type address =3D { street: string; city: string; zip: string; } [@@deriving jsonschema] type t =3D { name: string; age: int; email: string option; address: address; } [@@deriving jsonschema] let schema =3D Ppx_= deriving_jsonschema_runtime.json_schema t_jsonschema Will be turned into this schema { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "address": { "type": "object", "properties": { "zip": { "type": "string" }, "city": { "type": "string" }, "street": { "type": "string" } }, "required": [ "zip", "city", "street" ] }, "email": { "type": "string" }, "age": { "type": "integer" }, "name": { "type": "string" } }, "required": [ "address", "age", "name" ] } Some more advanced functionalities are documented in the readme. Please let me know if you see any important feature missing, if there are b= ugs, or if you have ideas of improvements. This project was originally started during a Ahrefs dojo, in parallel to th= e ICFP conference in Milan, as a way to learn how to write a ppx. I can't r= ecommend enough https://github.com/pedrobslisboa/ppx-by-example to get going.
opam 2.3.0~alpha1 Archive: https://discuss.ocaml.org/t/ann-opam-2-3-0-alpha1/15325/1
Kate announced As mentioned in our talk at the OCaml Workshop 2024, we de= cided to switch to a time-based release cycle (every 6 months), starting wi= th opam 2.3. As promised, we are happy to announce the first alpha release of opam 2.3.0.
What's new?
When loading a repository, opam now ignores files in packages' files/ directories which aren't listed in the extra-files fieldof the opam file. :warning: If you maintain an opam repositor= y, please read our blog post to make sure your repository stays compatible.
Packages requiring an unsupported version of opam are now marked una= vailable, instead of causing a repository error. This means an opam rep= ository can now allow smoother upgrade in the future opam list --latests-only: a new option to list only= the latest versions of packages --verbose-on: a new option to enable verbose output= for specified package names. opam switch import --deps-only: a new option to ins= tall only the dependencies of the root packages listed in the opam switch e= xport file opam switch list-available will now not display com= pilers flagged with avoid-version~/~deprecated unless --= all is given, meaning that the "trunk" build of OCaml no longer appe= ars to be the latest version The builtin-0install solver was improved and should= now be capable of being your default solver instead of builtin-mccs+= glpk. If you wish to give it a try, simply call opam option so= lver=3Dbuiltin-0install Most of the unhelpful conflict messages were fixed :flashlight:<= /li>
Various performance and other improvements were made and bugs were fixed. :open_book: You can read our blog post for more information about these changes and mor= e, and for even more details you can take a look at the release note or the changelog= .
Try it! The upgrade instructions are unchanged: For Unix systems bash -c "sh <(curl -fsSL https://raw.githubusercontent.com/ocaml/opam/ma= ster/shell/install.sh) --version 2.3.0~alpha1" or from PowerShell for Windows systems Invoke-Expression "& { $(Invoke-RestMethod https://raw.githubuserconten= t.com/ocaml/opam/master/shell/install.ps1) } -Version 2.3.0~alpha1" Please report any issues to the bug-tracker.
Other OCaml News From the ocaml.org blog Here are links from many OCaml blogs aggregated at the ocaml.org blog. Upcoming OCaml Events (Sep 22, 202= 4 and onwards) Eio From a User's Perspective: An In= terview With Simon Grondin Introducing the odoc= Cheatsheet: Your Handy Guide to OCaml Documentation Old CWN If you happen to miss a CWN, you can send me a message and I'll mail it to you, or go take a loo= k at the archive or the <= a href=3D"https://alan.petitepomme.net/cwn/cwn.rss">RSS feed of the archive= s. If you also wish to receive it every week by mail, you may subscribe to the= caml-list. Alan Schmitt

OCaml Weekly News

Table of Contents

ocaml-trace 0.8

Simon Cruanes announced

qcheck-lin and qcheck-stm 0.2

Jan Midtgaard announced

3rd editor tooling dev-meeting: 26th of September =F0=9F=A7=99=

vds announced

First release of hachis

Fran=C3=A7ois Pottier announced

Simon Cruanes then added

OCaml Platform Newsletter: June-August 2024

Thibaut Mattio announced

Dune Package Management (W4)

Native Support for Windows in opam 2.2 (W5)

Upgrading OCaml Package Documentation with Odoc 3.= 0 (W25)

Project-Wide References in OCaml Editors (W19)=

Bridging the Gap Between Merlin and OCaml LSP (W19)=

First alpha release of OCaml 5.3.0

octachron announced

Installation Instructions

Ascend - Dungeon RPG for your terminal

eir announced

first release of ppx_deriving_jsonschema

Louis Roch=C3=A9 announced

opam 2.3.0~alpha1

Kate announced

What's new?

Try it!

Other OCaml News

From the ocaml.org blog

Old CWN