ppxlib
ppxlib copied to clipboard
ocaml-ppx
Base library and tools for ppx rewriters
`let () = match () with Core.[] -> ()` fails, reporting `Core.[]` as having an identifier overlapping a pattern. I believe this is ultimately a parser bug in the source...
Addresses #363 about the associativity of `esequence`, and how this makes `deriving_inline` and `ocamlformat` clash. While I'm at it, update comment in `ppx_foo_deriver.ml` to reflect the module definition it generates.
Calling `esequence` on a list with more than two expressions in a `[@@deriving_inline]` gives the following error: ``` ----line 1 of ppx_contract_test.ml col 1 File "./ppx_contract_test.ml", line 1, characters 0-0:...
ppx_deriving supports an optional flag. From their docs: > It's possible to make deriving ignore a missing plugin rather than raising an error by passing an optional = true option,...
Apparently the ocaml parser gives the body of a let+ the same location as the whole let+ expression. This makes the locations check in ppxlib fail for any ppx that...
The documentation states the following about `[@@deriving_inline]`: https://github.com/ocaml-ppx/ppxlib/blob/9360b0c367ab5798895628bbb768e8685bdcb42f/doc/ppx-for-end-users.rst#L77-L83 However, this appears not to be true, as I observed by doing the following: 1. Added `[@@deriving_inline yaml][@@@end]` after a type declaration....
I have defined a deriver named "leq" with ppxlib, but I guess any ppxlib-based deriver would have the same issue. First, I use it in a test file as follows:...
Suppose you have code that uses `ppx_tools_versioned` and `ocaml-migrate-parsetree`. The code builds up an Ast_404 parsetree and then, as a last step, when it comes time to generate .ml and...
