ppx_import icon indicating copy to clipboard operation
ppx_import copied to clipboard

Less redundancy in type declarations and signatures

Results 17 ppx_import issues
Sort by recently updated
recently updated
newest added

Hi, I write and maintain a Camlp5-based work-alike for `ppx_import` (named `pa_ppx.import`), and I recently started to upgrade it for OCaml 5.2.0. I found that the old syntax ``` type...

Hi, I ran into https://github.com/ocaml-ppx/ppx_import/issues/89 as well, and I was able to resolve it by side-stepping the issue by pinning the package off of the latest git revision. Would it...

Code: ```ml (* foo.ml *) module type T = sig type _ t = None: unit t end (* bar.ml *) module type T = [%import: (module Foo.T)] ``` Result:...

The documentation says: > For module types, the replacements are specified using the standard `with` construct. Does that mean, like this? ```ml (* a.ml *) module type T = sig...

It will be helpful for the new module type syntax to make sure we support that case

**Note: This contains extra commits from #80, #81 and #82 that should be merged first** This PR implements the new module type syntax, so instead of `module type S_rec =...

Hello there, and many thanks for this wonderful extension. I am using `ppx_import` version 1.10.0. I just had a question about using the `[@with]` directive. My use case is that...

To match the new type declaration implemented in #68 `module type Hashable = [%import: (module Hashtbl.HashedType)]` would become `module type%import Hashable = Hashtbl.HashedType`