Right now, an mli file using Phat has to have signatures like:
val f : (Phat_pure.Std.abs, Phat_pure.Std.file) Phat_pure.Std.t
Even with the various type abbreviations we provide, you have to write at least Phat_pure.Std.abs_file. Opening Phat_pure.Std isn't an option because type t and item are too common.
Only solution I see is to define another module specifically for this purpose, with type ('a,'b) path = ('a,'b) t, and types like abs, rel, etc made directly available.
Right now, an mli file using Phat has to have signatures like:
Even with the various type abbreviations we provide, you have to write at least
Phat_pure.Std.abs_file
. OpeningPhat_pure.Std
isn't an option because typet
anditem
are too common.Only solution I see is to define another module specifically for this purpose, with
type ('a,'b) path = ('a,'b) t
, and types likeabs
,rel
, etc made directly available.