Cyclic dependencies

[ManasJayanth]

Sometimes, the classes have a cyclic dependencies, which when tried to generated bindings for, dune complains

Example:

let data_structures =
  ["Error"; "Layer"; "Timeline";]

Dependency cycle between the following files:
    _build/default/lib/.GES.objs/Layer.mli.all-deps
--> _build/default/lib/.GES.objs/Timeline.mli.all-deps
--> _build/default/lib/.GES.objs/Layer.mli.all-deps

Full gen.ml

[jhrdina]

Are there any best-practices on how to handle cyclic dependencies in OCaml bindings? I know that bs-webapi - BuckleScript (Reason/Ocaml) bindings to DOM API simply put all typedefs into one separate "Types" module... (in bs-webapi specifically it is named "Dom" and ships together with BS compiler, but you get the point...)

Is there any significant disadvantage in this approach?

[ManasJayanth]

@jhrdina I think this thread here will interest you.