When declaring the gospel model as a function (string -> string option), Ortac misinterprets it and separates the operator ->. It considers the arrow as a type constructor instead of the OCaml arrow, which is used for functions.
We have the type t modeling its content by a map of type string -> string option.
Following is the code generated by Ortac.
[...]
type nonrec state = {
contents: (string, string option) (->) }
[...]
It should be :
[...]
type nonrec state = {
contents: (string -> string option) }
[...]
When declaring the gospel model as a function
(string -> string option)
, Ortac misinterprets it and separates the operator->
. It considers the arrow as a type constructor instead of the OCaml arrow, which is used for functions.We have the type
t
modeling its content by a map of typestring -> string option
. Following is the code generated by Ortac.It should be :