OCaml

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

Follow-up issue to ocaml/ocaml#10275 (comment), noting CompCert's manual.

This is very low prio, but it usually happens that when touching Prims or some other file high in the dependency graph, we get spurious diffs in many other files. Since we check-in the snapshot, and we need to have it up-to-date, we get very verbose commits when nothing relevant changed. Plus, when something did change, it's hard to spot.

Example: I removed a few lines in prims and get things

Dune systematically buffers the output of commands so that their output is not mixed up during parallel builds. However, this is not ideal for interactive commands that require direct access to the terminal.

Currently, the only workaround is to run dune with -j 1 --no-buffer which is not ideal since it completely disables parallelism and also require a specific dune invocation.

Another ide

Describe the bug
The following (wrong) simple source file triggers an assertion failure.

> mkdir /tmp/bug
> cd /tmp/bug
> cat - > prop.ml
type t
type prop
external set : t -> prop -> t -> unit = "caml_js_get"
let set_if_some o p = function None -> () | Some v -> set o p v
> ocamlc -c prop.ml 
> js_of_ocaml compile prop.cmo 
js_of_ocaml: You found a bug. Please report it at htt

This might be a good way to reconcile Dream, Piaf, and the rest of the "ecosystem" for esy users.

The branch can probably be maintained by constantly cherry-picking a single commit that adds esy.json and subtracts src/vendor. This could even be done in CI in the long term, but probably we'd rather get rid of src/vendor by actually upstreaming or releasing the protocol projects, instead.