package ppxlib
Standard infrastructure for ppx rewriters
Install
Dune Dependency
Authors
Maintainers
Sources
ppxlib-0.30.0.tbz
sha256=dd4a63bde9d29b49810e04d7653937c932f177a941ca0e1982b6ad53ac442110
sha512=0a8c4fa894aaf445cb93213eaa32afb2772235da44aa28c917aba237731a44d5c2687bd960fca49bff62bbe0f9b3fdd9c15730313b429214ae281069f862ffdc
doc/ppxlib/Ppxlib/Expansion_context/Extension/index.html
Module Expansion_context.Extension
Source
Type of expansion contexts for extensions
Return the location of the extension point being expanded
Return the code path for the given context In Driver, Deriving and Extension, the context is initialized so that the file_path
component of the code_path
is determined from the first location found in the input AST. That means that:
- It's the empty string in empty structures or signatures
- It can be altered by line directives
Return the input name for the given context. In Driver, Deriving and Extension, the context argument is initialized so that the input_name
matches the input filename passed to the driver on the command line. That means that:
- It has a value even for empty files
- It is not affected by line directives
- It is
"_none_"
when usingDriver.map_structure
orDriver.map_signature
Can be used within a ppx preprocessor to know which tool is calling it "ocamlc"
, "ocamlopt"
, "ocamldep"
, "ocaml"
, ... .
Wrap a fun ~loc ~path
into a fun ~ctxt
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>