Attn: Development Editor, Latest OCaml Weekly News
Alan Schmitt <[email protected]>
| Newsgroups | gmane.comp.lang.caml.inria |
|---|---|
| Message-ID | <[email protected]> |
Hello
Here is the latest OCaml Weekly News, for the week of January 16 to 23,
2024.
Table of Contents
─────────────────
The OCaml community is signed up for Outreachy!
OCaml.org Newsletter: November and December 2023
Discussions on the future of the opam repository
dune 3.13
opam 2.2.0~beta1
Zipc 0.1.0
Other OCaml News
Old CWN
The OCaml community is signed up for Outreachy!
═══════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/the-ocaml-community-is-signed-up-for-outreachy/13892/1>
Sonja Heinze announced
──────────────────────
Hello everyone :wave:
Very good news: The OCaml community is signed up for the next
Outreachy round with four slots again!
[Outreachy] is a non-profit providing an over-arching structure for
open-source communities to offer three months long remote internships
to folks from underrepresented backgrounds in open-source.
Participating in Outreachy is a great opportunity for any open-source
community to work with new people, to increase its outreach, and to
open a first door to more diversity in the community.
The [OCaml community has a long history] of participating in that
wonderful initiative. There have been all kinds of OCaml projects that
interns have worked on, shaped, and given input to every year since
2014 (with the exception of 2017/18). And also this (Northern
hemisphere) winter, [we’re having three amazing interns with us].
So, as a first point, I want to say: Thank you, everyone! :heart: I
myself have started being involved in the OCaml Outreachy organization
only recently, while the whole community has been driving this for a
long time now. And that’s one of the many things that’s really really
nice about OCaml: There are nice industrial users, in this case [Jane
Street] and [Tarides], who’re willing to fund these kinds of efforts,
and there’s a whole lot of community members who’re willing to (and
enjoy!) getting involved, come up with projects, and mentor.
And that brings me to my second point: Do reach out to us if you also
want to form part of this. It’s up to you whether you want to write in
this thread or to DM @patricoferris and/or me (@pitag). Just like in
the last couple of rounds, I already have a few concrete people in
mind to reach out to for the upcoming round. However, I don’t know and
can’t know everyone in the community in person. So me reaching out to
people is working well so far, but people reaching out to us would be
much easier and a lot less restrictive.
PD: I’ll post here with the relevant dates for the next round once
they become more relevant. To already give one date: The deadline for
OCaml community members to submit internship projects is **Feb. 23,
2024**.
[Outreachy] <https://www.outreachy.org/>
[OCaml community has a long history] <https://ocaml.org/outreachy>
[we’re having three amazing interns with us]
<https://discuss.ocaml.org/t/welcoming-our-new-outrechy-interns/13652>
[Jane Street] <https://www.janestreet.com/>
[Tarides] <https://tarides.com/>
OCaml.org Newsletter: November and December 2023
════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/ocaml-org-newsletter-november-and-december-2023/13895/1>
Sabine Schmaltz announced
─────────────────────────
Welcome to the November and December 2023 edition of the OCaml.org
newsletter! This update has been compiled by the OCaml.org team. You
can find [previous updates] on Discuss.
Our goal is to make OCaml.org the best resource for anyone who wants
to get started and be productive in OCaml. The OCaml.org newsletter
provides an update on our progress towards that goal and an overview
of the changes we are working on.
We couldn’t do it without all the amazing OCaml community members who
help us review, revise, and create better OCaml documentation. Your
feedback enables us to better prioritise our work and make progress
towards our goal. Thank you!
This newsletter covers:
• *Learn Area:* We made substantial changes to the Learn Area UI,
introducing a new landing page and improving various elements on
the Learn Area’s subpages. Work on a documentation search feature
is in progress, and new documentation has been added or
substantially improved!
• *Upcoming Dark Mode*: We completed the UI designs for the upcoming
dark mode and our Outreachy intern has
started to implement the changes.
• *Announcing the Outreachy Interns*: We’re happy to welcome two
interns to work on OCaml projects!
• *General Improvements:* As usual, we also worked on general
maintenance and improvements based on user feedback, so we’re
highlighting some of our work below.
[previous updates] <https://discuss.ocaml.org/tag/ocamlorg-newsletter>
Open Issues for Contributors
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
We created many issues for external contributors. The majority of them
are suitable for OCaml beginners, and we’re happy to review and
provide feedback on your pull requests!
You can find [open issues for contributors here]!
[open issues for contributors here]
<https://github.com/ocaml/ocaml.org/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+no%3Aassignee>
Learn Area
╌╌╌╌╌╌╌╌╌╌
◊ 1. Redesign of the Learn Area
OCaml.org is undergoing an exciting transformation, and we’re thrilled
to share some key updates with you. Our main focus has been the
finalisation and approval of a new user interface (UI) design, aimed
at enhancing your experience. This update isn’t just about looks;
we’re ensuring the website is fully optimised for mobile and tablet
devices.
The collaboration between our team and users like you has been
instrumental in shaping the project. Your input and support have been
invaluable, and we’re grateful for the community’s involvement in
making this website the best it can be.
Our design system has seen several updates, including new components
like a variable landing page button, diverse icons (including social
media and OCaml icons like Dune and opam), enhanced text styles,
updated color variables, and more.
We’ve completed the designs for all pages of the Learn area. Each page
has been designed with attention to detail, ensuring consistency and
coherence across all versions.
If you’re curious and want to take a closer look at the designs, you
can access our [Figma Design Files]. Please be aware that the content
shown on the pages is not always accurate. We aim to provide our
designer with better content for the mockups and UI going forward.
The work on implementing the new designs for the light mode of the
Learn area have been completed in December!
*Relevant PRs and Activities:*
• Implemented Learn UI from Figma [ocaml/ocaml.org#1798]
• [@FatumaA] contributed: Improve platform page card styles
[ocaml/ocaml.org#1752]
• [@florentdrousset] contributed: Link exercises to tutorials
[ocaml/ocaml.org#1753]
• Add book links based on Figma design - [ocaml/ocaml.org#1834]
• WIP: Documentation Search Feature - [ocaml/ocaml.org#1871]
[Figma Design Files]
<https://www.figma.com/file/6BSOEqSsyQeulwLo2pjs9r/Untitled?type=design&node-id=0%3A1&mode=design&t=GwVxvrXItX7k8pP9-1>
[ocaml/ocaml.org#1798] <https://github.com/ocaml/ocaml.org/pull/1798>
[@FatumaA] <https://github/com/FatumaA>
[ocaml/ocaml.org#1752] <https://github.com/ocaml/ocaml.org/pull/1752>
[@florentdrousset] <https://github.com/florentdrousset>
[ocaml/ocaml.org#1753] <https://github.com/ocaml/ocaml.org/pull/1753>
[ocaml/ocaml.org#1834] <https://github.com/ocaml/ocaml.org/pull/1834>
[ocaml/ocaml.org#1871] <https://github.com/ocaml/ocaml.org/pull/1871>
◊ 2. OCaml Documentation
In November, we focussed on addressing and incorporating community
feedback on the “Getting Started” documents. The comments and
discussion on Discuss were so helpful. We encourage more of that!
We also worked on polishing “Basic Data Types” and “Values and
Functions.” Plus the team has been working on new “Modules,”
“Functors,” and “Libraries With Dune” documents, hoping to have it,
and the ones in community review (below), published before the end of
the year.
*Relevant PRs and Activities:*
• *In Progress:*
• Sets
• Maps
• Higher Order Functions
• *In Review (internal):*
• [Options]
• [Running Commands in a Switch]
• [Labelled Arguments]
• *In Review (community):*
• [Modules, Functors, Libraries With Dune] (see [Discuss])
• [File Manipulation] (see [Discuss Thread])
• [Polymorphic Variants] (see [Discuss Thread])
• *Published:*
• [Running Commands in an opam Switch]
• [Mutable State / Imperative Programming] (see [Discuss Thread])
• Announcement on Discuss: [New Tutorials on Basics of OCaml]
• [Basic Data Types] (see [Discuss Thread])
• [Functions and Values] (see [Discuss Thread])
• [Installing OCaml] (see [Discuss Thread])
• [A Tour Of OCaml] (see [Discuss Thread])
• [Your First OCaml Program] (see [Discuss Thread])
• [Introduction to opam Switches]
• [Fix Homebrew Errors on Apple M1]
• [Operators]
• [Error Handling] (see [Discuss Thread])
• [Arrays] (see [Discuss Thread])
• [Sequences] (see [Discuss Thread])
• *Other Activity*:
• We integrated pages from OCaml books into the Learn area,
reproduced on OCaml.org with permission - [ocaml/ocaml.org#1766]:
• Compiler & Runtime pages from [Real World OCaml], and
• Memoisation & Monads from [OCaml Programming: Correct +
Efficient + Beautiful]
• Rearranged the sections on the Language documentation tab -
[ocaml/ocaml.org#1756]
• Documentation formatting: Replace unsemantic blockquotes by
highlighting [ocaml/ocaml.org#1759]
• We improved the “Is OCaml Web Yet?” page, adding many more
packages and reworking the text to more accurately capture the
current state of the OCaml web ecosystem - [ocaml/ocaml.org#1843]
• Editing on Basic Data Types - [ocaml/ocaml.org#1827]
• Addressing suggestions from Issue #1762 - [ocaml/ocaml.org#1812]
• *Contributions:*
• [@benjamin-thomas] improved the `Map` document by providing a
better example that uses different types for the key and value
[ocaml/ocaml.org#1743]
• [@leostera] simplified the “Bootstrapping a Project with Dune”
guide - [ocaml/ocaml.org#1792]
• [@FatumaA] fixed a typo in “Tour of OCaml” [ocaml/ocaml.org#1739]
• [@binwang-dev] contributed: Fix type inconsistency in tutorial
[ocaml/ocaml.org#1757]
• [@J3RN] contributes: Fix escaping in “Your First OCaml Program” -
[ocaml/ocaml.org#1846]
• [@Sc4ramouche] contributes: Add comparison of std containers guide
to v3 docs
• [ocaml/ocaml.org#1828]
• [@Sc4ramouche] contributes: Fix typo in Tour of OCaml -
[ocaml/ocaml.org#1820]
• [@J3RN] contributes: Fix broken “Install Platform Tools” link -
[ocaml/ocaml.org#1841]
We started opening issues marked with “help wanted” to enable external
contributors to help improve the docs. The response has been
overwhelmingly positive, and we’re thrilled to keep this up and make
the OCaml documentation truly great with your help!
[Options] <https://github.com/ocaml/ocaml.org/pull/1800>
[Running Commands in a Switch]
<https://github.com/ocaml/ocaml.org/pull/1825>
[Labelled Arguments] <https://github.com/ocaml/ocaml.org/pull/1881>
[Modules, Functors, Libraries With Dune]
<https://github.com/ocaml/ocaml.org/pull/1778>
[Discuss]
<https://discuss.ocaml.org/t/draft-tutorials-on-modules-functors-and-libraries/>
[File Manipulation] <https://github.com/ocaml/ocaml.org/pull/1400>
[Discuss Thread]
<https://discuss.ocaml.org/t/help-review-the-new-file-manipulation-tutorial-on-ocaml-org/12638>
[Polymorphic Variants] <https://github.com/ocaml/ocaml.org/pull/1531>
[Discuss Thread]
<https://discuss.ocaml.org/t/new-draft-tutorial-on-polymorphic-variants/13485>
[Running Commands in an opam Switch]
<https://github.com/ocaml/ocaml.org/pull/1825>
[Mutable State / Imperative Programming]
<https://github.com/ocaml/ocaml.org/pull/1529>
[Discuss Thread]
<https://discuss.ocaml.org/t/draft-tutorial-on-mutability-loops-and-imperative-programming/13504>
[New Tutorials on Basics of OCaml]
<https://discuss.ocaml.org/t/new-tutorials-on-basics-of-ocaml/13396>
[Basic Data Types] <https://github.com/ocaml/ocaml.org/pull/1514>
[Discuss Thread]
<https://discuss.ocaml.org/t/ocaml-org-tutorial-revamping-contd-basic-datatypes/12985>
[Functions and Values] <https://github.com/ocaml/ocaml.org/pull/1512>
[Discuss Thread]
<https://discuss.ocaml.org/t/ocaml-org-tutorial-revamping-cond-values-and-functions/13005>
[Installing OCaml] <https://ocaml.org/docs/installing-ocaml>
[Discuss Thread]
<https://discuss.ocaml.org/t/help-revamping-the-getting-started-tutorials-in-ocaml-org/12749>
[A Tour Of OCaml] <https://ocaml.org/docs/tour-of-ocaml>
[Your First OCaml Program] <https://ocaml.org/docs/your-first-program>
[Introduction to opam Switches]
<https://ocaml.org/docs/opam-switch-introduction>
[Fix Homebrew Errors on Apple M1] <https://ocaml.org/docs/arm64-fix>
[Operators] <https://ocaml.org/docs/operators>
[Error Handling] <https://ocaml.org/docs/error-handling>
[Discuss Thread]
<https://discuss.ocaml.org/t/ann-new-get-started-documentation-on-ocaml-org/13269>
[Arrays] <https://ocaml.org/docs/arrays>
[Discuss Thread]
<https://discuss.ocaml.org/t/feedback-needed-new-arrays-tutorial-on-ocaml-org/12683>
[Sequences] <https://ocaml.org/docs/sequences>
[Discuss Thread]
<https://discuss.ocaml.org/t/creating-a-tutorial-on-sequences/12091>
[ocaml/ocaml.org#1766] <https://github.com/ocaml/ocaml.org/pull/1766>
[Real World OCaml] <https://dev.realworldocaml.org/>
[OCaml Programming: Correct + Efficient + Beautiful]
<https://cs3110.github.io/textbook/cover.html>
[ocaml/ocaml.org#1756] <https://github.com/ocaml/ocaml.org/pull/1756>
[ocaml/ocaml.org#1759] <https://github.com/ocaml/ocaml.org/pull/1759>
[ocaml/ocaml.org#1843] <https://github.com/ocaml/ocaml.org/pull/1843>
[ocaml/ocaml.org#1827] <https://github.com/ocaml/ocaml.org/pull/1827>
[ocaml/ocaml.org#1812] <https://github.com/ocaml/ocaml.org/pull/1812>
[@benjamin-thomas] <https://github.com/benjamin-thomas>
[ocaml/ocaml.org#1743] <https://github.com/ocaml/ocaml.org/pull/1743>
[@leostera] <https://github.com/leostera>
[ocaml/ocaml.org#1792] <https://github.com/ocaml/ocaml.org/pull/1792>
[@FatumaA] <https://github/com/FatumaA>
[ocaml/ocaml.org#1739] <https://github.com/ocaml/ocaml.org/pull/1739>
[@binwang-dev] <https://github.com/binwang-dev>
[ocaml/ocaml.org#1757] <https://github.com/ocaml/ocaml.org/pull/1757>
[@J3RN] <https://github.com/J3RN>
[ocaml/ocaml.org#1846] <https://github.com/ocaml/ocaml.org/pull/1846>
[@Sc4ramouche] <https://github.com/Sc4ramouche>
[ocaml/ocaml.org#1828] <https://github.com/ocaml/ocaml.org/pull/1828>
[ocaml/ocaml.org#1820] <https://github.com/ocaml/ocaml.org/pull/1820>
[ocaml/ocaml.org#1841] <https://github.com/ocaml/ocaml.org/pull/1841>
Upcoming Dark Mode
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
In December, [oyenuga17] started to implement the new dark mode on
OCaml.org. Plans are to complete and activate the dark mode based on
browser / operating system preferences by early March.
We continuously merge small patches into ocaml.org, and you can take a
look at completed dark mode pages on <https://staging.ocaml.org>. We
placed a button at the bottom of the page to toggle the dark mode on
staging (this is not going to be released, it is only a means for us
to review the dark mode pages).
*Relevant Activities and PRs:*
• Implement dark mode on learn area landing page -
[ocaml/ocaml.org#1836]
• UI design for dark mode on all OCaml.org pages, and resulting Design
System changes
[oyenuga17] <https://github.com/oyenuga17>
[ocaml/ocaml.org#1836] <https://github.com/ocaml/ocaml.org/pull/1836>
Announcing the Outreachy Interns
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
In November, we reviewed and rated the Outreachy contributions for the
dark mode project and the GUI project and selected the two interns.
[@oyenuga17] is working with the OCaml.org team on implementing the
dark mode, while [@IdaraNabuk] has been selected for the GUI project.
Congratulations [@IdaraNabuk] and [@oyenuga17]!
Since the Outreachy application period ended in October, we list all
the remaining pull requests done on Outreachy Issues in the “General
Improvements” section below.
[@oyenuga17] <https://github.com/oyenuga17>
[@IdaraNabuk] <https://github.com/IdaraNabuk>
General Improvements
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
*Most Important Changes TLDR*:
• There’s now a self-hosted Plausible.io instance for OCaml.org,
accessible at <https://plausible.ci.dev/ocaml.org>!
• You can see the different OCaml teams (Compiler, Platform,
Packaging, Infrastructure, OCaml.org) and the maintainers of
relevant repositories at the new governance page at
<https://ocaml.org/governance>!
• The OCaml Logo now has a dedicated page at <https://ocaml.org/logo>!
• We’re now displaying a package’s README on the package overview
page.
• You can now [list upcoming events] with date and time on
<https://ocaml.org/community>.
• OCaml.org now has social media images, so that sharing OCaml.org
links looks nicer.
Many thanks go out to the many contributors who helped improve
OCaml.org in November and December. Find them listed below!
*Relevant PRs and Activities:*
• Features / Improvements:
• Added a governance page that lists the maintainers and dev
meetings of the compiler, all the projects of the OCaml Platform,
and the ocaml.org infrastructure - [ocaml/ocaml.org#1239]
• [@IdaraNabuk] contributed: Added the ability to record upcoming
events to the community page - [ocaml/ocaml.org#1717]
• [@Girish-Jangam] contributed: Added a page for the OCaml logo -
[ocaml/ocaml.org#1711]
• Add ability to disable an OCaml Planet source / fix scraper and
scrape missing planet posts - [ocaml/ocaml.org#1734]
• [@leostera] contributed: Package search UX improvements -
[ocaml/ocaml.org#1691]
• Added an OpenSearch manifest, so you can add the OCaml packages
search to your browser search bar
• Made search input in main navbar gain tab-focus earlier
• Set tabindex=“1” for the in-package search input on the package
documentation page
• Autofocus the search inupt on the package search results page
• [@mays4] contributed: Add links to CONTRIBUTING.md for all data
items that can be contributed - [ocaml/ocaml.org#1682]
• [@m-spitfire] contributed: Entries on the changelog page are now
paginated - [ocaml/ocaml.org#1751]
• Add missing social media images to OCaml.org HTML metadata. Now,
posts shared on social media have the OCaml logo as image, which
is much better than having no image - [ocaml/ocaml.org#1784]
• We’re now displaying a package’s README on the package overview
page. This was part of one of the design options from the package
area redesign earlier this year. However, it wasn’t entirely clear
that this was the right thing to do. More confirmation came up in
terms of people asking for this, so we did it. -
[ocaml/ocaml.org#1832]
• Update to Tailwind CSS 3.3.6 - [ocaml/ocaml.org#1850]
• Added table of contents to jump to individual sections on “Is
OCaml Web yet” - [ocaml/ocaml.org#1849]
• [@RWUBAKWANAYO] contributed: Improved responsive layout on
releases page - [ocaml/ocaml.org#1716]
• [@kiyov09] contributed: Reduced the number of news items in the
blog page to have a similar height to the OCaml Planet column -
[ocaml/ocaml.org#1754]
• [@oyenuga17] contributed: Improved responsive collapsing of the
table on the papers page - [ocaml/ocaml.org#1741]
• Bugfixes:
• Adjust CSS order of elements of main nav, starting from 0 -
[ocaml/ocaml.org#1745]
• Set correct background color on learn tabs select element -
[ocaml/ocaml.org#1746]
• [@Solar-Rays] contributed: Remove links from outreachy project
description to prevent overflow - [ocaml/ocaml.org#1764]
• Patch upstream dependency `river` to fall back to feed entry’s
`id` if `links` tag does not exist. This allows more feeds to be
scraped successfully. - [tarides/river#11]
• Added missing Code of Conduct Route - [ocaml/ocaml.org#1781]
• Added missing ’Platform Tools’ link in footer -
[ocaml/ocaml.org#1788]
• [@AndroGenius-codes] contributed: Fixed a bug in pagination where
the page number “1” was displayed twice when all the results would
fit on a single page - [ocaml/ocaml.org#1729]
• [@Demmythetechie] contributed: Add `word-wrap: break-word` to the
Tailwind Typography prose class to prevent long URLs in content
areas from overflowing - [ocaml/ocaml.org#1722]
• [@AndroGenius-codes] contributed: Shorten text on Outreachy
Projects link on the community page to prevent overflow -
[ocaml/ocaml.org#1749]
• [@oyenuga17] contributed: Render search query as input value on
the papers page and the releases page - [ocaml/ocaml.org#1747]
• [@FatumaA] contributed: Added spacing below “See All Releases”
button on homepage - [ocaml/ocaml.org#1740]
• [@RWUBAKWANAYO] contributed: Resolve text styling issue in release
list headers [ocaml/ocaml.org#1773]
• [@kevanantha] contributed: Fix invalid link for exercises
[ocaml/ocaml.org#1802]
• Other:
• [@oyenuga17] contributed: Replaced dependency `omd` with `cmarkit`
- [ocaml/ocaml.org#1642]. Thanks for this excellent and
challenging contribution!
• Remove Yoshi tool - [ocaml/ocaml.org#1735]
• Removed dream-dashboard, it was replaced a self-hosted
plausible.io instance - [ocaml/ocaml.org#1736]
• Rename Tutorials->Documentation in meta title of Learn Area -
[ocaml/ocaml.org#1789]
• Content:
• Added “Introduction to Functional Programming and the Structure of
Programming Languages using OCaml” to the books section -
[ocaml/ocaml.org#1744]
• Added the changelog for opam.2.2.0~alpha3 - [ocaml/ocaml.org#1771]
• Update title of Platform Roadmap document to ’OCaml Platform
Roadmap’ - [ocaml/ocaml.org#1790]
• Add some feeds to the OCaml Planet - [ocaml/ocaml.org#1779]
• Added “Practical OCaml” blog to the Planet -
[ocaml/ocaml.org#1806]
• [@caisar-platform] contributed: Fix broken link in CEA Research
Engineer offer. [ocaml/ocaml.org#1787]
• [@KihongHeo] contributed: Add KAIST as an academic institution
[ocaml/ocaml.org#1791]
• [@hetzenmat] contributes: Fix wrong release date for 5.1.1 -
[ocaml/ocaml.org#1858]
• [@zapashcanon] contributes: Fix order of presentations -
[ocaml/ocaml.org#1859]
• [@oyenuga17] contributes: add outreachy blog | introduce yourself
- [ocaml/ocaml.org#1848]
• [@IdaraNabuk] contributed: Add Outreachy Blog Post to OCaml Planet
[ocaml/ocaml.org#1878]
• Added ’Retrofitting Parallelism onto OCaml’ paper -
[ocaml/ocaml.org#1875]
[list upcoming events]
<https://github.com/ocaml/ocaml.org/blob/main/CONTRIBUTING.md#content-upcoming_event>
[ocaml/ocaml.org#1239] <https://github.com/ocaml/ocaml.org/pull/1239>
[@IdaraNabuk] <https://github.com/IdaraNabuk>
[ocaml/ocaml.org#1717] <https://github.com/ocaml/ocaml.org/pull/1717>
[@Girish-Jangam] <https://github.com/Girish-Jangam>
[ocaml/ocaml.org#1711] <https://github.com/ocaml/ocaml.org/pull/1711>
[ocaml/ocaml.org#1734] <https://github.com/ocaml/ocaml.org/pull/1734>
[@leostera] <https://github.com/leostera>
[ocaml/ocaml.org#1691] <https://github.com/ocaml/ocaml.org/pull/1691>
[@mays4] <https://github.com/mays4>
[ocaml/ocaml.org#1682] <https://github.com/ocaml/ocaml.org/pull/1682>
[@m-spitfire] <https://github.com/m-spitfire>
[ocaml/ocaml.org#1751] <https://github.com/ocaml/ocaml.org/pull/1751>
[ocaml/ocaml.org#1784] <https://github.com/ocaml/ocaml.org/pull/1784>
[ocaml/ocaml.org#1832] <https://github.com/ocaml/ocaml.org/pull/1832>
[ocaml/ocaml.org#1850] <https://github.com/ocaml/ocaml.org/pull/1850>
[ocaml/ocaml.org#1849] <https://github.com/ocaml/ocaml.org/pull/1849>
[@RWUBAKWANAYO] <https://github.com/RWUBAKWANAYO>
[ocaml/ocaml.org#1716] <https://github.com/ocaml/ocaml.org/pull/1716>
[@kiyov09] <https://github.com/kiyov09>
[ocaml/ocaml.org#1754] <https://github.com/ocaml/ocaml.org/pull/1754>
[@oyenuga17] <https://github.com/oyenuga17>
[ocaml/ocaml.org#1741] <https://github.com/ocaml/ocaml.org/pull/1741>
[ocaml/ocaml.org#1745] <https://github.com/ocaml/ocaml.org/pull/1745>
[ocaml/ocaml.org#1746] <https://github.com/ocaml/ocaml.org/pull/1746>
[@Solar-Rays] <https://github.com/Solar-Rays>
[ocaml/ocaml.org#1764] <https://github.com/ocaml/ocaml.org/pull/1764>
[tarides/river#11] <https://github.com/tarides/river/pull/11>
[ocaml/ocaml.org#1781] <https://github.com/ocaml/ocaml.org/pull/1781>
[ocaml/ocaml.org#1788] <https://github.com/ocaml/ocaml.org/pull/1788>
[@AndroGenius-codes] <https://github.com/AndroGenius-codes>
[ocaml/ocaml.org#1729] <https://github.com/ocaml/ocaml.org/pull/1729>
[@Demmythetechie] <https://github.com/Demmythetechie>
[ocaml/ocaml.org#1722] <https://github.com/ocaml/ocaml.org/pull/1722>
[ocaml/ocaml.org#1749] <https://github.com/ocaml/ocaml.org/pull/1749>
[ocaml/ocaml.org#1747] <https://github.com/ocaml/ocaml.org/pull/1747>
[@FatumaA] <https://github/com/FatumaA>
[ocaml/ocaml.org#1740] <https://github.com/ocaml/ocaml.org/pull/1740>
[ocaml/ocaml.org#1773] <https://github.com/ocaml/ocaml.org/pull/1773>
[@kevanantha] <https://github.com/kevanantha>
[ocaml/ocaml.org#1802] <https://github.com/ocaml/ocaml.org/pull/1802>
[ocaml/ocaml.org#1642] <https://github.com/ocaml/ocaml.org/pull/1642>
[ocaml/ocaml.org#1735] <https://github.com/ocaml/ocaml.org/pull/1735>
[ocaml/ocaml.org#1736] <https://github.com/ocaml/ocaml.org/pull/1736>
[ocaml/ocaml.org#1789] <https://github.com/ocaml/ocaml.org/pull/1789>
[ocaml/ocaml.org#1744] <https://github.com/ocaml/ocaml.org/pull/1744>
[ocaml/ocaml.org#1771] <https://github.com/ocaml/ocaml.org/pull/1771>
[ocaml/ocaml.org#1790] <https://github.com/ocaml/ocaml.org/pull/1790>
[ocaml/ocaml.org#1779] <https://github.com/ocaml/ocaml.org/pull/1779>
[ocaml/ocaml.org#1806] <https://github.com/ocaml/ocaml.org/pull/1806>
[@caisar-platform] <https://github.com/caisar-platform>
[ocaml/ocaml.org#1787] <https://github.com/ocaml/ocaml.org/pull/1787>
[@KihongHeo] <https://github.com/KihongHeo>
[ocaml/ocaml.org#1791] <https://github.com/ocaml/ocaml.org/pull/1791>
[@hetzenmat] <https://github.com/hetzenmat>
[ocaml/ocaml.org#1858] <https://github.com/ocaml/ocaml.org/pull/1858>
[@zapashcanon] <https://github.com/zapashcanon>
[ocaml/ocaml.org#1859] <https://github.com/ocaml/ocaml.org/pull/1859>
[ocaml/ocaml.org#1848] <https://github.com/ocaml/ocaml.org/pull/1848>
[ocaml/ocaml.org#1878] <https://github.com/ocaml/ocaml.org/pull/1878>
[ocaml/ocaml.org#1875] <https://github.com/ocaml/ocaml.org/pull/1875>
Discussions on the future of the opam repository
════════════════════════════════════════════════
Archive:
<https://discuss.ocaml.org/t/discussions-on-the-future-of-the-opam-repository/13898/1>
Raphaël Proust announced
────────────────────────
The [default opam repository] has been getting larger and larger with
an ever increasing number of packages. This is somewhat of a good sign
for the active community of OCaml developers. But it is also a
challenge for its use, for its maintenance, and for the execution of
its CI.
A discussion on the future of the opam repository is happening and we
(the opam repository maintainers) would like to invite OCaml
developers at large to participate.
You can read the dedicated github issue [Requests for comments: how
does opam-repository scale?] and share opinions there.
You can also join the public meeting held Wednesday 2024-01-24 at
14:00 GMT on <https://meet.jit.si/opam-repo-meeting>.
Please do prefer the issue (rather than this thread) to discuss the
issue (to keep the discussion in a central location).
[default opam repository] <https://github.com/ocaml/opam-repository/>
[Requests for comments: how does opam-repository scale?]
<https://github.com/ocaml/opam-repository/issues/23789>
dune 3.13
═════════
Archive: <https://discuss.ocaml.org/t/ann-dune-3-13/13911/1>
Etienne Millon announced
────────────────────────
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.
Generate Conflicts File for Menhir Grammars ([#9512], [@nojb])
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
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.
[#9512] <https://github.com/ocaml/dune/pull/9512>
[@nojb] <https://github.com/nojb>
Cached Directory Targets ([#9535], [@rleshchinskiy])
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
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.
[#9535] <https://github.com/ocaml/dune/pull/9535>
[@rleshchinskiy] <https://github.com/rleshchinskiy>
Dynamic Module List ([#9578], [@nojb])
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
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.
Here is the full changelog:
[#9578] <https://github.com/ocaml/dune/pull/9578>
[@nojb] <https://github.com/nojb>
Added
╌╌╌╌╌
• 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 (ie 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)
Changed
╌╌╌╌╌╌╌
• Check that package names in `(depends)' and related fields in
`dune-project' are well-formed. (#9472, fixes #9270, @ElectreAAS)
Fixed
╌╌╌╌╌
• 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)
opam 2.2.0~beta1
════════════════
Archive: <https://discuss.ocaml.org/t/ann-opam-2-2-0-beta1/13913/1>
Kate announced
──────────────
On behalf of the opam dev team, I’m happy to announce the first beta
release of opam 2.2.0.
What’s new in this beta?
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌
• `opam init' on Windows now requires you to choose which Git to use.
Git for Windows is now recommended by default, though Cygwin’s Git
can of course still be used. See the blog post linked below for more
info on why choose one over the other.
• when compiling opam on Windows with MinGW, the resulting opam binary
now contains `libstdc++' instead of requiring the DLL to be
distributed alongside it or to be present in the environment during
compilation
• fix `opam env' containing carriage return on Cygwin - `eval $(opam
env)' now works from a Cygwin bash terminal
• as well as a bunch of bug fixes and improvements
You’ll find these features presented in the [blog post], and for some
extra details you can take a look at the [release note] or the
[changelog].
We encourage you to try out this beta release, instructions are
detailed in the [blog post], in particular [if you’re using Windows]
for which we provide a – /still experimental/ – pre-built binary.
On Unix-like systems though, to upgrade, simply run:
┌────
│ bash -c "sh <(curl -fsSL https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh) --version
│ 2.2.0~beta1"
└────
Happy hacking, *<> <> The opam team <> <>* :camel:
[blog post] <https://opam.ocaml.org/blog/opam-2-2-0-beta1/>
[release note] <https://github.com/ocaml/opam/releases/tag/2.2.0-beta1>
[changelog] <https://github.com/ocaml/opam/blob/2.2.0-beta1/CHANGES>
[blog post] <https://opam.ocaml.org/blog/opam-2-2-0-beta1>
[if you’re using Windows]
<https://opam.ocaml.org/blog/opam-2-2-0-beta1/#How-to-Test-opam-on-Windows>
Zipc 0.1.0
══════════
Archive: <https://discuss.ocaml.org/t/ann-zipc-0-1-0/13388/2>
Daniel Bünzli announced
───────────────────────
Zipc 0.2.0 has been [released] to the opam-repository.
It provides a few encoding bug fixes courtesy of Valentin
Gatien-Baron’s investigations on round tripping `docx' files with
`zipc'.
He also suggested not to ignore `zip'’s declared metadata about
decompression size to allow clients to easily cap memory consumption
for decoding untrusted zip files (breaking change).
The details are in the [release notes] and many thanks to him.
[released] <https://github.com/ocaml/opam-repository/pull/25105>
[release notes]
<https://github.com/dbuenzli/zipc/blob/fa4bbfe4e70119665f39769bec9cfac9e0729304/CHANGES.md#v020-2024-01-22-la-forclaz-vs>
Other OCaml News
════════════════
>From the ocaml.org blog
───────────────────────
Here are links from many OCaml blogs aggregated at [the ocaml.org
blog].
• [Outreachy Blog: Everyone Struggles]
• [The OCaml Community]
• [What are Data Races? And do They Threaten Your Business?]
• [Concepts of Functional Programming]
[the ocaml.org blog] <https://ocaml.org/blog/>
[Outreachy Blog: Everyone Struggles]
<https://idaranabuk.com/blog/everyone_struggles>
[The OCaml Community] <https://idaranabuk.com/blog/ocaml_community>
[What are Data Races? And do They Threaten Your Business?]
<https://tarides.com/blog/2024-01-17-what-are-data-races-and-do-they-threaten-your-business>
[Concepts of Functional Programming]
<https://priver.dev/blog/functional-programming/concepts-of-functional-programming/>
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 look at [the archive] or the [RSS feed of the
archives].
If you also wish to receive it every week by mail, you may subscribe
to the [caml-list].
[Alan Schmitt]
[send me a message] <mailto:[email protected]>
[the archive] <https://alan.petitepomme.net/cwn/>
[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>
[caml-list] <https://sympa.inria.fr/sympa/info/caml-list>
[Alan Schmitt] <https://alan.petitepomme.net/>