package uniq
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=998588f1053cf03161a4bded6d7f8068c88de497e77fc0bbca81a5234fa444d5
sha512=53d4ee5ad8c01e19a2e1fbda86266768d118f78566b82f0c736338ce2c12258185a5f4dbb90bf0da37a7528098266ec81861bdcfea29e55daa3122a4f3a1daca
doc/uniq.mmeta/Uniq_meta/index.html
Module Uniq_metaSource
val search :
roots:Fpath.t list ->
?predicates:string list ->
Path.t ->
((Fpath.t * Assoc.t) list, [> `Msg of string ]) resultSearch the META file for the given path.
Synthesis all artifacts described into the given META files into Uniq_info.t values.
val from_cmi_to_impl :
roots:Fpath.t list ->
packages:package list ->
?stdlib:Fpath.t ->
?disambiguate:(Modname.t -> Path.t list -> Path.t) ->
Fpath.t ->
(archive option, [> `Msg of string ]) resultfrom_cmi_to_impl ~roots cmi associates the given cmi artifact with the ocamlfind package that ships it. It returns the package's Path.t, the directory holding its META file and its descriptor — a triple whose (directory, descriptor) projection is directly consumable by to_artifacts to obtain the implementation archives. It returns None when no package under roots owns the cmi (e.g. a project-local unit).
The association is done by directory first (the cmi physically lives in its package's directory) and falls back to an interface digest comparison when the directory is ambiguous or does not match.
stdlib, when provided, is the OCaml standard library directory (e.g. from the compiler configuration of the chosen toolchain). A cmi sitting there is associated with the synthetic stdlib package, since the standard library ships no META file.
val archives_of :
roots:Fpath.t list ->
?predicates:string list ->
archive ->
(Uniq_info.t list, [> `Msg of string ]) result/