REReleaseCandidat·Apr 2, 2024
Not just the standard library, but a whole ecosystem around it.
And their own compiler. https://github.com/ocaml-flambda/ocaml-jst
In Property-based testing in practice [pdf]ocaml-flambda
ocaml-jst
OCaml2023–2024
ocaml-flambda / ocaml-jst
ocaml-jst
OCaml plus Jane Street extensions
5Distinct people
7Mentions
0Explicit recommenders
74GitHub stars
What to know before exploring
What it is
OCaml plus Jane Street extensions
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month7 dated mentions
Observed mentions: 2023-04-17 12:05:43 UTC to 2024-04-02 08:35:30 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 1 | 1 | 0 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 5 | 1 | 4 |
| Jun 2023 | 2023-06-01 00:00:00 UTC | 2023-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2023 | 2023-07-01 00:00:00 UTC | 2023-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2023 | 2023-08-01 00:00:00 UTC | 2023-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2023 | 2023-09-01 00:00:00 UTC | 2023-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2023 | 2023-10-01 00:00:00 UTC | 2023-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2023 | 2023-11-01 00:00:00 UTC | 2023-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2023 | 2023-12-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2024 | 2024-01-01 00:00:00 UTC | 2024-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2024 | 2024-02-01 00:00:00 UTC | 2024-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2024 | 2024-03-01 00:00:00 UTC | 2024-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2024 | 2024-04-01 00:00:00 UTC | 2024-05-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesFrom the post:
> Even without explicit mode annotations, the compiler can statically determine which variables may escape their enclosing region. Such variables are assigned the global mode; all others are automatically inferred to be local.
There's a little more info about mode inference in the proposal:
https://github.com/ocaml-flambda/ocaml-jst/blob/main/jane/do...
So arguments to "public functions" do require explicit annotations in order to be local, but otherwise the compiler is able to infer locality and this acts as a transparent optimization.
In Oxidizing OCaml: LocalityThey always had their own version of the compiler:
https://github.com/ocaml-flambda/ocaml-jst/tree/main
Many of their changes have been ported to the 'official' OCaml compiler.
In Oxidizing OCaml: LocalityIt's this proposal:
https://github.com/ocaml-flambda/ocaml-jst/blob/main/jane/do...
and these problems:
https://github.com/ocaml-flambda/ocaml-jst/blob/main/jane/do...
In Oxidizing OCaml: LocalityI believe this is an explanation (part of) of this proposal:
https://github.com/ocaml-flambda/ocaml-jst/blob/main/jane/do...
In Oxidizing OCaml: LocalityData races are bad (OCaml/Jane Street)
3 points · Open discussion