Unit_info.Artifact(3)

πŸ’– Unit_info.Artifact β€” from the OCaml library πŸ’–

okay bestie, this is the Unit_info.Artifact page from the OCaml library, and it's literally all about build artifacts. no cap, it's short and iconic ✨


✨ NAME ✨

Unit_info.Artifact β€” Build artifacts πŸ› οΈπŸ’…


🧸 Module 🧸

the module line is exactly Module Unit_info.Artifact β€” main character energy, fr fr πŸ‘‘


πŸ“š Documentation πŸ“š

the docs open with exactly:

Module Artifact : sig end

πŸŽ€ Build artifacts πŸŽ€

type t

t is the metadata for a single compilation artifact, and the metadata includes these exact three lines, bestie β€” copied verbatim so nothing gets lost πŸ’–:

-the module name associated to the artifact
-the filesystem path
-the input source file if it exists

so yes: the module name, the filesystem path, and the input source file if it exists. that's the whole vibe check 🌸


πŸ’œ val source_file : t -> Unit_info.filename option

source_file a is the source file of a if it exists. literally only if it exists β€” no guessing, no cap πŸ’…


πŸ¦‹ val prefix : t -> Unit_info.file_prefix

prefix a is the filename prefix of the compilation artifact. cute little prefix moment ✨


πŸŽ€ val filename : t -> Unit_info.filename

filename u is the filesystem path for a compilation artifact. yes, it uses u in the docs β€” we keep it exactly, periodt πŸ’–


🌈 val modname : t -> Unit_info.modname

modname a is the module name of the compilation artifact. iconic, short, slay πŸ‘‘


πŸ“ val from_filename : Unit_info.filename -> t

from_filename filename reconstructs the module name lax_modname_from_source filename associated to the artifact filename . yes, that space before the period is exactly how it's written β€” we don't "fix" it, bestie πŸ˜­πŸ’€


xoxo, your Unix bestie πŸ’… β€” from OCamldoc, dated 2026-06-22, for Unit_info.Artifact(3) 🫢✨

πŸ“¦ where this page comes from