In a real set of bindings we have a C finalizer that closes the handle automatically. When testing this we have code which looks something like the simplified example below: let handle_closed = ref 0 let final _ = incr handle_closed let () = assert (!handle_closed = 0) let () = let obj = ref […

Without flambda, the following code doesn’t work: let obj = ref [] let () = Gc.finalise obj Here, even if obj does not appear in the .mli file, it is considered a toplevel value and never collected. With flambda, the criterion for toplevel values is not syntactic anymore; anything not under a fun…

OCaml 5: forcing objects to be collected and finalized

Learning

rwmjones June 27, 2023, 12:25pm 2

Here’s the real test: libguestfs/ocaml/t/guestfs_065_implicit_close.ml at master · libguestfs/libguestfs · GitHub

Topic		Replies	Views
Downsides to calling Gc.full_major at exit? Learning bindings	15	1685	April 25, 2020
OCaml heap "fsck" and forcing collection of unreachable objects Community gc	3	497	May 31, 2023
Is there a way to turn off garbage collection inside of one function? Learning gc	15	2360	April 27, 2020
Calling OCaml from C - random segfaults Learning	6	1270	January 10, 2018
Gc.finalise and let open struct .. end Learning gc	4	566	April 16, 2021

OCaml 5: forcing objects to be collected and finalized

Related topics