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?

The following example:

let () = (
    assert false
  )

Prints: Exception: Assert_failure ("./test.ml", 1, 9).

That is, the assertion is reported to be on line 1, when the actual assertion statement is on line 2.

A formula like forall x1. forall. x2. exists x3. phi gets resugared to, and hence pretty printed as, forall x1 x2 x3. phi. The bug is in the uncurry function in FStar.Syntax.Reguar.fs.

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

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.

Running the following piece of code with js_of_ocaml crashes the node environment (it generates a too large string, and memory consumption grows unbounded). Running the same code as a binary directly doesn't have this behavior.

let () =
  let ob = Buffer.create 2096 in
  let oc = open_out "test-file" in
  let seq =
    Seq.unfold
      (fun b ->
        if b < 100 * 100 * 100