Konstantin A. Olkhovskiy

 I can confirm that adding these lines (denoted by green line at the left) does not change the outcome, it still runs into segmentation fault. `runtime_test` is called only...

Maybe `ocaml::Pointer` should always store *just pointers* in OCaml-managed memory, this way we're 100% safe if OCaml is willing to move them around. Currently any use of value inside `ocaml::Pointer`...

This [SO answer](https://stackoverflow.com/a/5369026/1635516) also confirms that custom blocks are subject to move like any other OCaml heap objects. > I will try it out later today when I get a...

Thanks @tizoc for valuable pointers! @zshipko I'm not sure why it's necessary to port DynBox magic into ocaml-rs if it could just be used from `ocaml_interop` package possibly via some...

Okay, I found some time to brush up the code that I had and actually published it on Github, meet [ocaml-lwt-interop](https://github.com/Lupus/ocaml-lwt-interop)! I described how things work in README and even...

I keep hitting the same kind of segfaul once again it seems. Easy to work-around, but I thought maybe there's some nice way to avoid it altogether... I've started [a...

> I just pushed a commit to the ocaml5 branch to root arguments by default - I wonder if that will have any effect on the segfault? @zshipko I'm pretty...

Turns out that my segfaults were caused by me ignoring some safety constraints for spawning tasks, see [this reply](https://users.rust-lang.org/t/restrict-reference-from-being-borrowed-by-async-weird-segfault-in-ocaml-rust-interop/95636/5) to my topic on rust forum. @zshipko have you had a...

If there is no need to ignore anything else than `_build`, I would probably just stop doing that. It's a higly confusing impilit behavior.

I've also got bitten by that when tried to tell dune that I need my `.cargo` dir in the build environment as a dependency. It was just silently ignored when...