package ocamlformat-mlx-lib

You can search for identifiers within the package.

in-package search v0.2.0

OCaml .mlx Code Formatter

Install

Dune Dependency

github.com Readme Changelog Edit opam file Versions (3)

Authors

Maintainers

A

Andrey Popp <me@andreypopp.com>

Sources

0.26.2.0.tar.gz

md5=4b32d3b57da54157a0cd8f772094f4bc

sha512=367eeb5d81060a3efb584796cc72cc75d974975bb9b18be6284a86f5937edb90927368fd80e00b3f4c1894e609b4a1503c20d4495c624560243e5055f905390a

doc/ocamlformat-mlx-lib.odoc_parser/Odoc_parser/index.html

Module `Odoc_parser`Source

Parser for ocamldoc formatted comments.

Sourcetype t

type t is the result of parsing.

Sourceval parse_comment : location:Lexing.position -> text:string -> t

parse_comment ~location ~text parses text as an ocamldoc formatted string. The parser will try to recover from any invalid syntax encountered, and therefore this will always produce a result without raising exceptions with zero or more warnings. The location passed in should represent the start of the content of the documentation comment - so for a line such as

  (** A comment starting in the first column (0) *)

the location should represent the space immediately before the A, so the in the 4th column (e.g. {... pos_bol=0; pos_cnum=3 })

Sourcemodule Ast : sig ... end

Abstract syntax tree representing ocamldoc comments

Sourcemodule Loc : sig ... end

Locations in files.

Sourcemodule Warning : sig ... end

Warnings produced during parsing.

Sourceval warnings : t -> Warning.t list

Extract any warnings from the parser result.

Sourceval ast : t -> Ast.t

Extract the Ast.t from the parser result.

Sourceval position_of_point : t -> Loc.point -> Lexing.position

Helper function to turn the internal representation of positions back into the usual representation in the Lexing module. Note that this relies on the information passed in parse_comment, and hence requires the result of that call in addition to the Loc.point being converted.