ppx_import
ppx_import copied to clipboard
Less redundancy in type declarations and signatures
Seems required for new version according to https://github.com/gildor478/ounit#transition-to-ounit2. I'm completely new to the whole ocaml stack, but can build only with such change.
With the syntax `type t = [%import: Foo.bla]`, the `[%import: Foo.bla]` is written at a place where the OCaml parser expects a [core type extension node](https://github.com/ocaml/ocaml/blob/cce52acc7c7903e92078e9fe40745e11a1b944f0/parsing/parsetree.mli#L149-L150). But `ppx_import` doesn't only...
I'm writing a version of ppx_import for camlp5, and I noticed that there is only import for individual type-declarations. But just as we don't like to write down the RHS...
e.g. ``` # module M = struct type t = int end;; module M : sig type t = int end # type t = [%import: M.t] [@@deriving show];; Error:...
It seems a large use case for *import* is, as stated in the readme, for use with *deriving* to derive functions for types that you do not own. It is...
If I try to derive `eq` from imported types, I get the following error message: ``` Error: eq cannot be derived for fully abstract types ``` The setup is as...
Hi, I'd like to redeclare many of my currently abstract types as private so their contents are visible to ocamldebug. If ppx_import allowed me to change an imported type's visibility...