Bruno Deferrari

@g2p sounds good. I'm revising some stuff, and changing a few names. I will let you know once it is ready.

Merged some changes I have been working on since last month earlier today and released a new version. The main thing that changed is that function calls now center around...

Note that `OCamlClosure` is not exposed and only meant for internal use, but you are right, all it's functions, although not marked `unsafe`, are. `ocaml!` is the only public interface...

Hello @macthecadillac. Is this a macOS program? from a quick search what I found is that what is missing is that you need to link the `Security.framework` framework (how that...

@mrmr1993 at a first glance it looks good, but will re-check tomorrow. One thing, you have to bump the version of the root Cargo.toml file too. About the commented function...

If the "root" serializer has to add more data, it is because you are serializing something different. Using the `User` example, a list of `User`s is not the same as...

Solved in part by #31 (which was #24).

Just got bitten by this.

I see Chez 10.0.0 got released and one of the changes is: > AArch64 (64-bit Arm), RV64G (64-bit RISC-V), and LoongArch64 architectures are supported I just pushed an updated Makefile...

@mt-caret +1 to a proc macro based approach. You can kind of consider the `ocaml_export!` macro to be deprecated, it is just that there is nothing else right now. Initially...