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?

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

Right now to be able to use caramelc in an Erlang or Elixir project, we sort of have to manually invoke it in the right place and then also compile the caramel stdlib erlang sources and make sure its available. An entire dance.

It'd be useful to have a mix plugin to see what the interop from the Elixir side feels like so that we can just create a new mix project, and if you have caramel ava