Nicolas Jeannerod
Nicolas Jeannerod
In fact, `ppx_deriving_yojson` fixed its dependencies 2 months ago. But the new OPAM file isn't in the official repositories. I'll try with it and see if the issue is fixed...
OK, I can still reproduce with Yojson 1.7.0. But this isn't so surprising. The problem here is not that we are using `List.map` on large lists. Our trees aren't large...
It is to be noted that dash also has a pretty weird behaviour on such a script.
We are waiting for the links for Menhir & Visitors to be fixed: - in the OPAM repository with https://github.com/ocaml/opam-repository/pull/18697 (fixed) - in the OPAM repository for Windows with https://github.com/fdopen/opam-repository-mingw/pull/95...
OK, CI is turning again but (as suspected) Windows is unhappy. I will look into it.
To reproduce: - Put your self in a bytecode-only environment. For instance using OPAM: - `opam switch create 4.04.2+bytecode-only` - `eval $(opam env)` - Check that you don't have an...
I would very much like such an option with the same use case in mind: containerisation and CI. Actually, I would use it from time to time on my local...
Indeed, Plutus Core is strict, which makes a lot of sense. So I guess I would expect ` || ` to be compiled lazily just like the `case` and `if-then-else`...
Oh. I did not realise they were functions and not operators of the language. This indeed explains everything. Is there a reason why that is? I suppose it can come...
Since it is not an issue but the correct semantics, I suppose we can close this issue?