Module `Expansion_context.Deriver`Source

Sourcetype t

Type of expansion contexts for derivers

Sourceval derived_item_loc : Ppxlib.Expansion_context.Deriver.t -> Ppxlib.Location.t

Return the location of the item to which the deriver is being applied

Sourceval code_path : Ppxlib.Expansion_context.Deriver.t -> Ppxlib.Code_path.t

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

Sourceval input_name : Ppxlib.Expansion_context.Deriver.t -> string

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 using Driver.map_structure or Driver.map_signature

Sourceval tool_name : Ppxlib.Expansion_context.Deriver.t -> string

Can be used within a ppx preprocessor to know which tool is calling it "ocamlc", "ocamlopt", "ocamldep", "ocaml", ... .

Source

val with_loc_and_path : 
  (loc:Ppxlib.Location.t -> path:string -> 'a) ->
  ctxt:Ppxlib.Expansion_context.Deriver.t ->
  'a

Wrap a fun ~loc ~path into a fun ~ctxt

Sourceval inline : Ppxlib.Expansion_context.Deriver.t -> bool

Whether the derived code is going to be inlined in the source

Module Expansion_context.DeriverSource

Module `Expansion_context.Deriver`Source