hhugo
hhugo
Any idea how much breakage the change of API generates ?
It seems we could now complete the api with `BigInt64Array` and `BigUint64Array`. One could do that in a subsequent PR. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt64Array
The PR definitely need a changelog entry
@OlivierNicole, can you look at Jerome suggestion ? and rebase and squash commits ?
I ended up squashing during the merge
This breaks ezjs_crypto. I am adding a constraint in opam. See https://github.com/ocaml/opam-repository/pull/26932/commits/e1c4e8e30ca0cd9014ea023f8f536367601e6986
@vouillon, can you take a look ?
> @hhugo As far as I understand the code, we are only reading shapes from `cma` files, not from `cmo` files. Should we use `Compilation_context.dep_graphs` for that? I've just pushed...
@vouillon, can you review this again ? I've addressed your comments.
ping @vouillon