I'm currently explore OCaml and his ecosystem, you can read the beginning of my journey with this 2 articles:

https://gilwath.com/articles/from_scala_to_ocaml_part1.html

https://gilwath.com/articles/from_scala_to_ocaml_part2.html

#scala #OCaml

I've released a new version of my raylib-ocaml bindings. It now supports raylib 6.0.0 and modularizes the library into the modules of upstream raylib.

https://github.com/tjammer/raylib-ocaml/releases/tag/2.0.0

Handling of constants is also improved and since this breaks the API (in minor ways) I decided to give it a new major version.

PR to opam is underway

#ocaml #raylib

OCaml Weekly News, for the week of May 26 to June 02, 2026

https://discuss.tchncs.de/post/61423956

The #OCaml Weekly News for 2026-06-02 is out

https://alan.petitepomme.net/cwn/2026.06.02.html

A spike for an OCaml test framework: https://codeberg.org/m-e-leypold/my-rosetta/src/branch/main/spike/ocaml-test-framework/example.tests.ml#L62

While we're at it: A rather generic Makefile for #ocaml: https://codeberg.org/m-e-leypold/my-rosetta/src/branch/main/spike/ocaml-test-framework/Makefile

#macro_rules!

Right methodology, not nearly powerful enough

#proc_macros

Lisp-like methodology, but syn crate and DIY the AST, more importantly, the unholy diabolical compile times involved

#crabtime

idk, give reviews

Only if they learned from #Zig's #comptime/ #OCaml's #ppx

LET ME WRITE #RUST **AND** MANIPULATE ASTs, NOT AN XOR OF THEM

I've finally managed to tick off a box for my raylib bindings that I wanted to solve for literal years.

Like upstream raylib, we now separate the library into modules of `core`,
`text`, `shapes`, `textures`, `models`, and `audio`. The types all live
in `core`. This allows linking only a subset of the library surface, for
smaller binaries. A super-module `raylib` re-exports everything to link
the whole binding (including `rlgl`), so there is no breakage for users.

#ocaml #raylib